[PATCH 1/1] ftrace: fix typo in ftrace.txt file

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




commit 43bf3fdddfd6b0ac65ef59bec3c79d9f9064e8bd
Author: GeunSik,Lim <leemgs1@xxxxxxxxx>
Date:   Thu May 14 13:39:18 2009 +0900

    ftrace: fix typo in ftrace.txt file.
    
    Fix typo about chart to map the kernel priority to
    user land priorities.
    
    About sched_setscheduler(2)
    Processes scheduled under SCHED_FIFO or SCHED_RR
    can have a static priority in the range 1 to 99.
    
        Signed-off-by: GeunSik Lim <geunsik.lim@xxxxxxxxxxx>

diff --git a/Documentation/trace/ftrace.txt b/Documentation/trace/ftrace.txt
index fd9a3e6..0e17632 100644
--- a/Documentation/trace/ftrace.txt
+++ b/Documentation/trace/ftrace.txt
@@ -518,9 +518,14 @@ priority with zero (0) being the highest priority and the nice
 values starting at 100 (nice -20). Below is a quick chart to map
 the kernel priority to user land priorities.
 
-  Kernel priority: 0 to 99    ==> user RT priority 99 to 0
-  Kernel priority: 100 to 139 ==> user nice -20 to 19
-  Kernel priority: 140        ==> idle task priority
+ Kernel priority: 0(high) to 99(low)    ==> user RT priority 99(high) to 1(low)
+ Kernel priority: 100(high) to 139(low) ==> user nice -20(high) to 19(low)
+ Kernel priority: 140                   ==> idle task priority
+
+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)
 
 The task states are:
 


-----------------------------------------------
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 43bf3fdddfd6b0ac65ef59bec3c79d9f9064e8bd
Author: GeunSik,Lim <leemgs1@xxxxxxxxx>
Date:   Thu May 14 13:39:18 2009 +0900

    ftrace: fix typo in ftrace.txt file.
    
    Fix typo about chart to map the kernel priority to
    user land priorities.
    
    About sched_setscheduler(2)
    Processes scheduled under SCHED_FIFO or SCHED_RR
    can have a static priority in the range 1 to 99.
    
        Signed-off-by: GeunSik Lim <geunsik.lim@xxxxxxxxxxx>

diff --git a/Documentation/trace/ftrace.txt b/Documentation/trace/ftrace.txt
index fd9a3e6..0e17632 100644
--- a/Documentation/trace/ftrace.txt
+++ b/Documentation/trace/ftrace.txt
@@ -518,9 +518,14 @@ priority with zero (0) being the highest priority and the nice
 values starting at 100 (nice -20). Below is a quick chart to map
 the kernel priority to user land priorities.
 
-  Kernel priority: 0 to 99    ==> user RT priority 99 to 0
-  Kernel priority: 100 to 139 ==> user nice -20 to 19
-  Kernel priority: 140        ==> idle task priority
+ Kernel priority: 0(high) to 99(low)    ==> user RT priority 99(high) to 1(low)
+ Kernel priority: 100(high) to 139(low) ==> user nice -20(high) to 19(low)
+ Kernel priority: 140                   ==> idle task priority
+
+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)
 
 The task states are:
 

[Index of Archives]     [RT Stable]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux