summaryrefslogtreecommitdiffstats
path: root/Documentation/scheduler
diff options
context:
space:
mode:
authorGeunSik Lim <leemgs1@gmail.com>2009-05-28 10:36:14 +0900
committerIngo Molnar <mingo@elte.hu>2009-05-29 16:21:09 +0200
commitf04d82b7e0c63d0251f9952a537a4bc4d73aa1a9 (patch)
treede32c62ffd0051884fd5e157009fffe7c82fd7b0 /Documentation/scheduler
parent294ae4011530d008c59c4fb9847738e39228821e (diff)
downloadlinux-f04d82b7e0c63d0251f9952a537a4bc4d73aa1a9.tar.gz
linux-f04d82b7e0c63d0251f9952a537a4bc4d73aa1a9.tar.bz2
linux-f04d82b7e0c63d0251f9952a537a4bc4d73aa1a9.zip
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 Signed-off-by: GeunSik Lim <geunsik.lim@samsung.com> CC: Steven Rostedt <rostedt@goodmis.org> Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> LKML-Reference: <new-submission> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'Documentation/scheduler')
-rw-r--r--Documentation/scheduler/sched-rt-group.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/scheduler/sched-rt-group.txt b/Documentation/scheduler/sched-rt-group.txt
index eb74b014a3f8..1df7f9cdab05 100644
--- a/Documentation/scheduler/sched-rt-group.txt
+++ b/Documentation/scheduler/sched-rt-group.txt
@@ -187,7 +187,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).