Skip to contentSkip to conversation

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

PATCH In review GeunSik Lim 3 participants 4 messages May 12, 2009 Documentation

lore
Share & tools
lore
#0 lore raw

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

Dear Ingo,

I found typo about the range of static priority ( = realtime priority ) in "./Documentation/scheduler/sched-rt-group.txt" file.

If I don't understand static priority levels, Correct 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 to 99 --> User Space RT priority 99 to 0
Kernel Space priority: 100 to 139 --> User Space nice -20 to 19

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 to 99 --> User Space RT priority 99 to 0
Kernel Space priority: 100 to 139 --> User Space nice -20 to 19

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
Quoted 8 lines · GeunSik Lim

Dear Ingo,

I found typo about the range of static priority ( = realtime priority ) in "./Documentation/scheduler/sched-rt-group.txt" file.

If I don't understand static priority levels, Correct me.

Right, that 'confusion' stems from the fact that our in-kernel priority lists do consider all 140 priorities.

The patch looks good though.

Quoted 38 lines

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 to 99 --> User Space RT priority 99 to 0
Kernel Space priority: 100 to 139 --> User Space nice -20 to 19

Documentation/scheduler/sched-rt-group.txt +1 -2
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/
-----------------------------------------------

#2 lore raw
Quoted 33 lines · Peter Zijlstra
Quoted 8 lines · GeunSik Lim

Dear Ingo,

I found typo about the range of static priority ( = realtime priority ) in "./Documentation/scheduler/sched-rt-group.txt" file.

If I don't understand static priority levels, Correct me.

Right, that 'confusion' stems from the fact that our in-kernel priority lists do consider all 140 priorities.

The patch looks good though.

Quoted 18 lines

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 to 99 --> User Space RT priority 99 to 0
Kernel Space priority: 100 to 139 --> User Space nice -20 to 19

Documentation/scheduler/sched-rt-group.txt +0 -0
index 5ba4d3f..1537146 100644
@@ -169,7 +169,7 @@ get their allocated time.
 
Quoted 4 lines

Documentation/scheduler/sched-rt-group.txt get their allocated time. · line 172

Quoted 4 lines
Documentation/scheduler/sched-rt-group.txt +1 -1
 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

SCHED_FIFO goes from 1 to 99. So it's either 0-98 or 1-99. From sched_setscheduler(2):

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).

Ingo

#3 lore raw

2009/5/12 Ingo Molnar <[email protected]>:

Quoted 44 lines · Peter Zijlstra
Quoted 34 lines · GeunSik Lim
Quoted 8 lines

Dear Ingo,

I found typo about the range of static priority ( = realtime priority ) in "./Documentation/scheduler/sched-rt-group.txt" file.

If I don't understand static priority levels, Correct me.

Right, that 'confusion' stems from the fact that our in-kernel priority lists do consider all 140 priorities.

The patch looks good though.

Quoted 18 lines

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   to 99   --> User Space RT priority 99 to 0 Kernel Space priority: 100 to 139  --> User Space nice -20 to 19

Documentation/scheduler/sched-rt-group.txt +0 -0
index 5ba4d3f..1537146 100644
@@ -169,7 +169,7 @@ get their allocated time.
 
Quoted 4 lines

Documentation/scheduler/sched-rt-group.txt

Quoted 4 lines

 Implementing SCHED_EDF might take a while to complete. Priority Inheritance is the biggest challenge as the current linux PI infrastructure is geared towards

Documentation/scheduler/sched-rt-group.txt +1 -1
-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

SCHED_FIFO goes from 1 to 99. So it's either 0-98 or 1-99. From sched_setscheduler(2):

Quoted 5 lines

      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).

       Ingo

Thank you for explanation about userspace rt priority's range like sched_setscheduler(2).

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.

So, I think that the below summary is right.
* Kernel Space priority: 0(high) to 99(low) --> User Space RT priority 99(high) to 0(low)

Is it incorrect?

Signature · 11 lines
Regards,
GeunSik Lim
--
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/
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html