From: Steven Rostedt <rostedt@goodmis.org>
To: GeunSik Lim <leemgs1@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
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: Re: [PATCH 1/1] ftrace: fix typo in ftrace.txt file
Date: Tue, 19 May 2009 22:00:04 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0905192153080.7816@gandalf.stny.rr.com> (raw)
In-Reply-To: <1242783692.31161.56.camel@centos51>
On Wed, 20 May 2009, GeunSik Lim wrote:
>
>
> 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)
Shouldn't that be:
Kernel priority: 0(high) to 98(low) ==> user RT priority 99(high) to 1(low)
100 items does not map to 99. Which begs the question, what can have
internal kernel priority 99?
> + 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
This line is confusing. "static priorty 0" really has no meaning here.
Those now enter the "nice" priorities, and this statement does not
represent what is shown in the ftrace output.
> +can have a static priority in the range 1 to 99.
> + (reference: $> man 2 sched_setscheduler)
>
-- Steve
next prev parent reply other threads:[~2009-05-20 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 1:41 GeunSik Lim
2009-05-20 2:00 ` Steven Rostedt [this message]
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=alpine.DEB.2.00.0905192153080.7816@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=a.p.zijlstra@chello.nl \
--cc=leemgs1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®