Skip to contentSkip to conversation

sched: fix typo in sched-rt-group.txt file

PATCH New GeunSik Lim 2 participants 6 messages May 21, 2009 – May 29, 2009

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

v3 cover sched: fix typo in sched-rt-group.txt file

Dear Ingo,

I made 2 patch files again about static prioriy levels to map between kernel-space and usper-space according to opinions and helps from Peter, Ingo, Steven.

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

Please, drop my previous version and merge this.

Changelog since V3
o Modified kernel static priority to map user rt priority ( 99 ~ 1).
- Archives: http://marc.info/?l=linux-kernel&m=124279443511114&w=2
- before : Kernel priority: 0(high) to 99(low) --> user RT priority 99(high) to 1(low)
- after : Kernel priority: 0(high) to 98(low) --> user RT priority 99(high) to 1(low)

Changelog since V2
o Modified description static priority(SCHED_FIFO,SCHED_RR) levels of user-space using sched_setscheduler(2)
- Archives: http://marc.info/?t=124211992800003&r=1&w=2
- before : Kernel priority: 0(high) to 99(low) --> user RT priority 99(high) to 0(low)
- after : Kernel priority: 0(high) to 99(low) --> user RT priority 99(high) to 1(low)
o Modified static priority related quick chart of sched_switch section in ./Documentation/trace/ftrace.txt file

Changelog since V1
o Changed static priority levels of kernel-space. ( 0 ~ 139 --> 0-99 ) in sched-rt-group.txt file

commit d6af702008117ca489a2f5476239d1688a517e98

Author: GeunSik,Lim <[email protected]>
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 98(low) --> User Space RT priority 99(high) to 1(low) with SCHED_RR or SCHED_FIFO
* Kernel Space priority 99 --> sched_priority is not used in scheduling decisions (it must be specified as 0)
* Kernel Space priority 100(high) to 139(low)--> User Space nice -20(high) to 19(low)

For processes scheduled under one of the normal scheduling policies (SCHED_OTHER, SCHED_IDLE, SCHED_BATCH), sched_priority is not used in scheduling decisions (it must be specified as 0).

Processes scheduled under one of the real-time policies(SCHED_FIFO,SCHED_RR) have a sched_priority value in the range 1 (low) to 99 (high).
(reference: http://www.kernel.org/doc/man-pages/online/pages/man2/sched_setscheduler.2.html)

Documentation/scheduler/sched-rt-group.txt +1 -1
index 5ba4d3f..1537146 100644
@@ -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 [email protected] 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) [email protected]
2) [email protected] , [email protected]
HomePage: http://intomail.dnip.net/invain/me/
-----------------------------------------------

commit d6af702008117ca489a2f5476239d1688a517e98

Author: GeunSik,Lim <[email protected]>
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 98(low) --> User Space RT priority 99(high) to 1(low) with SCHED_RR or SCHED_FIFO
* Kernel Space priority 99 --> sched_priority is not used in scheduling decisions (it must be specified as 0)
* Kernel Space priority 100(high) to 139(low)--> User Space nice -20(high) to 19(low)

For processes scheduled under one of the normal scheduling policies (SCHED_OTHER, SCHED_IDLE, SCHED_BATCH), sched_priority is not used in scheduling decisions (it must be specified as 0).

Processes scheduled under one of the real-time policies(SCHED_FIFO,SCHED_RR) have a sched_priority value in the range 1 (low) to 99 (high).
(reference: http://www.kernel.org/doc/man-pages/online/pages/man2/sched_setscheduler.2.html)

Documentation/scheduler/sched-rt-group.txt +1 -1
index 5ba4d3f..1537146 100644
@@ -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).
 
#1 lore raw

v3 cover description about static priority.

Signature · 1 line
-- 
Quoted 1 line

From c2e8f308730c87010d50a72f80ede6b7f308497e Mon Sep 17 00:00:00 2001

From: GeunSik,Lim <[email protected]>
Date: Thu, 28 May 2009 10:08:00 +0900
Subject: [PATCH 0/2] description about static priority.

Dear Ingo Molnar,

This is static priority description related patch files.

Please, merge my patch.

Thanks,

GeunSik,Lim (2):
ftrace: fix typo about map of kernel priority in ftrace.txt file.
sched: fix typo in sched-rt-group.txt file

 Documentation/scheduler/sched-rt-group.txt |    2 +-
 Documentation/trace/ftrace.txt             |   15 ++++++++++++---
 2 files changed, 13 insertions(+), 4 deletions(-)

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

GeunSik Lim ( S A M S U N G E L E C T R O N I C S )
e-Mail :1) [email protected]
2) [email protected] , [email protected]
HomePage: http://blog.naver.com/invain/
-----------------------------------------------

#2 lore raw

Re: [RESEND] [PATCH 0/2 V3] description about static priority.

Quoted 1 line · GeunSik Lim

Please, merge my patch.

ok, I've queued them up for my next push to ingo.

#3 lore raw

Re: [RESEND] [PATCH 0/2 V3] description about static priority.

Quoted 4 lines · Peter Zijlstra
Quoted 1 line · GeunSik Lim

Please, merge my patch.

ok, I've queued them up for my next push to ingo.

Thanks Peter.

Quoted 2 lines
Signature · 10 lines
Regards,
GeunSik Lim ( SAMSUNG ELECTRONICS)
Blog : http://blog.naver.com/invain/
e-Mail: [email protected]
           [email protected] , [email protected]
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
#4 lore raw

PATCH RESEND v3 1/2 ftrace: fix typo about map of kernel priority in ftrace.txt file.

In reply to GeunSik Lim
Quoted 3 lines

From 5764d50e29e08d86f7f3b7dff66d7c1ad4762ff8 Mon Sep 17 00:00:00 2001

From: GeunSik,Lim <[email protected]>
Date: Thu, 28 May 2009 09:57:28 +0900
Subject: [PATCH 1/2] ftrace: fix typo about map of kernel priority 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 (user-space) static priority in the range 1 to 99. (reference: http://www.kernel.org/doc/man-pages/online/pages/
man2/sched_setscheduler.2.html)

* From: Steven Rostedt
0 to 98 - maps to RT tasks 99 to 1 (SCHED_RR or SCHED_FIFO)

99 - maps to internal kernel threads that want to be lower than RT tasks but higher than SCHED_OTHER tasks. Although I'm not sure if any kernel thread actually uses this. I'm not even sure how this can be set, because the internal sched_setscheduler function does not allow for it.

100 to 139 - maps nice levels -20 to 19. These are not set via sched_setscheduler, but are set via the nice system call.

140 - reserved for idle tasks.

---
 Documentation/trace/ftrace.txt |   15 ++++++++++++---
 1 files changed, 12 insertions(+), 3 deletions(-)
Documentation/trace/ftrace.txt +12 -3
index fd9a3e6..e362f50 100644
@@ -518,9 +518,18 @@ 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 Space                     User Space
+ ===============================================================
+   0(high) to  98(low)     user RT priority 99(high) to 1(low)
+                           with SCHED_RR or SCHED_FIFO
+ ---------------------------------------------------------------
+  99                       sched_priority is not used in scheduling
+                           decisions(it must be specified as 0)
+ ---------------------------------------------------------------
+ 100(high) to 139(low)     user nice -20(high) to 19(low)
+ ---------------------------------------------------------------
+ 140                       idle task priority
+ ---------------------------------------------------------------
 
 The task states are:
 
Signature · 14 lines
1.6.3.1


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

GeunSik Lim (  S A M S U N G     E L E C T R O N I C S  )
e-Mail  :1) [email protected]
         2) [email protected] , [email protected]
HomePage: http://blog.naver.com/invain/
-----------------------------------------------
#5 lore raw

PATCH RESEND v3 2/2 sched: fix typo in sched-rt-group.txt file

In reply to GeunSik Lim
Quoted 4 lines

From c2e8f308730c87010d50a72f80ede6b7f308497e Mon Sep 17 00:00:00 2001

From: GeunSik,Lim <[email protected]>
Date: Thu, 28 May 2009 09:59:46 +0900
Subject: [PATCH 2/2] sched: fix typo in sched-rt-group.txt file

Fix typo about static priority's range.

Kernel Space User Space
===============================================================
0(high) to 98(low) user RT priority 99(high) to 1(low)
with SCHED_RR or SCHED_FIFO
---------------------------------------------------------------
99 sched_priority is not used in scheduling
decisions(it must be specified as 0)
---------------------------------------------------------------
100(high) to 139(low) user nice -20(high) to 19(low)
---------------------------------------------------------------
140 idle task priority
---------------------------------------------------------------
* ref) http://www.kernel.org/doc/man-pages/online/pages/man2/sched_setscheduler.2.html

---
 Documentation/scheduler/sched-rt-group.txt |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
Documentation/scheduler/sched-rt-group.txt +1 -1
index 5ba4d3f..1537146 100644
@@ -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).
 
Signature · 15 lines
1.6.3.1



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

GeunSik Lim (  S A M S U N G     E L E C T R O N I C S  )
e-Mail  :1) [email protected]
         2) [email protected] , [email protected]
HomePage: http://blog.naver.com/invain/
-----------------------------------------------