From: GeunSik Lim <leemgs1@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Steven Rostedt <rostedt@goodmis.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
tglx <tglx@linutronix.de>, williams <williams@redhat.com>
Subject: [PATCH 1/1] ftrace: fix typo in ftrace.txt file
Date: Wed, 20 May 2009 10:41:32 +0900 [thread overview]
Message-ID: <1242783692.31161.56.camel@centos51> (raw)
[-- Attachment #1: Type: text/plain, Size: 2028 bytes --]
commit 43bf3fdddfd6b0ac65ef59bec3c79d9f9064e8bd
Author: GeunSik,Lim <leemgs1@gmail.com>
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@samsung.com>
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@vger.kernel.org
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@samsung.com
2) leemgs@gmail.com , leemgs1@gmail.com
HomePage: http://intomail.dnip.net/invain/me/
-----------------------------------------------
[-- Attachment #2: fix-typo-chart-map-priority-ftrace.patch --]
[-- Type: text/x-patch, Size: 1500 bytes --]
commit 43bf3fdddfd6b0ac65ef59bec3c79d9f9064e8bd
Author: GeunSik,Lim <leemgs1@gmail.com>
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@samsung.com>
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:
next reply other threads:[~2009-05-20 1:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 1:41 GeunSik Lim [this message]
2009-05-20 2:00 ` [PATCH 1/1] ftrace: fix typo in ftrace.txt file Steven Rostedt
2009-05-20 4:40 ` GeunSik Lim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1242783692.31161.56.camel@centos51 \
--to=leemgs1@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).