[PATCH 0/1] sched: fix typo in sched-rt-group.txt file

[GeunSik Lim]

Dear Ingo,


I made 2 patch files again about static prioriy levels according to ingo's advice 
and explanation. (Reference: http://marc.info/?t=124211992800003&r=1&w=2 archives. )

Fix static priority related range and chart map(userspace/kernelspace) of ftrace.
   - about chart map of static priority in  ftrace.txt file
   - about static priority levels(range) in sched-rt-group.txt file 


commit d6af702008117ca489a2f5476239d1688a517e98
Author: GeunSik,Lim <leemgs1@xxxxxxxxx>
Date:   Tue May 12 17:20:32 2009 +0900

    sched: fix typo in sched-rt-group.txt file
    
    Fix typo about static priority's range.

    * Kernel Space priority 0(high) to 99(low)   --> User Space RT priority 99(high) to 1(low)
    * Kernel Space priority 100(high) to 139(low)--> User Space nice -20(high) to 19(low)

    Processes scheduled with SCHED_OTHER or SCHED_BATCH must be assigned
    the static priority 0. Processes scheduled under SCHED_FIFO or SCHED_RR 
    can have a static priority in the range 1 to 99. 
    (reference: $> man 2 sched_setscheduler)
    
    Signed-off-by: GeunSik Lim <geunsik.lim@xxxxxxxxxxx>

diff --git a/Documentation/scheduler/sched-rt-group.txt b/Documentation/scheduler/sched-rt-group.txt
index 5ba4d3f..1537146 100644
--- a/Documentation/scheduler/sched-rt-group.txt
+++ b/Documentation/scheduler/sched-rt-group.txt
@@ -169,7 +169,7 @@ get their allocated time.
 
 Implementing SCHED_EDF might take a while to complete. Priority Inheritance is
 the biggest challenge as the current linux PI infrastructure is geared towards
-the limited static priority levels 0-139. With deadline scheduling you need to
+the limited static priority levels 0-99. With deadline scheduling you need to
 do deadline inheritance (since priority is inversely proportional to the
 deadline delta (deadline - now).
 



-----------------------------------------------
To unsubscribe from this list: send the line "unsubscribe linux-***" 
in the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

GeunSik Lim (ELS - OS Group - S/W Lab - SAIT - SAMSUNG)
e-Mail  :1) geunsik.lim@xxxxxxxxxxx
         2) leemgs@xxxxxxxxx , leemgs1@xxxxxxxxx
HomePage: http://intomail.dnip.net/invain/me/
-----------------------------------------------
commit d6af702008117ca489a2f5476239d1688a517e98
Author: GeunSik,Lim <leemgs1@xxxxxxxxx>
Date:   Tue May 12 17:20:32 2009 +0900

    sched: fix typo in sched-rt-group.txt file
    
    Fix typo about static priority's range.

    * Kernel Space priority 0(high) to 99(low)   --> User Space RT priority 99(high) to 1(low)
    * Kernel Space priority 100(high) to 139(low)--> User Space nice -20(high) to 19(low)

    Processes scheduled with SCHED_OTHER or SCHED_BATCH must be assigned
    the static priority 0. Processes scheduled under SCHED_FIFO or SCHED_RR 
    can have a static priority in the range 1 to 99. 
    (reference: $> man 2 sched_setscheduler)
    
    Signed-off-by: GeunSik Lim <geunsik.lim@xxxxxxxxxxx>

diff --git a/Documentation/scheduler/sched-rt-group.txt b/Documentation/scheduler/sched-rt-group.txt
index 5ba4d3f..1537146 100644
--- a/Documentation/scheduler/sched-rt-group.txt
+++ b/Documentation/scheduler/sched-rt-group.txt
@@ -169,7 +169,7 @@ get their allocated time.
 
 Implementing SCHED_EDF might take a while to complete. Priority Inheritance is
 the biggest challenge as the current linux PI infrastructure is geared towards
-the limited static priority levels 0-139. With deadline scheduling you need to
+the limited static priority levels 0-99. With deadline scheduling you need to
 do deadline inheritance (since priority is inversely proportional to the
 deadline delta (deadline - now).