From: GeunSik Lim <leemgs1@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
tglx <tglx@linutronix.de>, williams <williams@redhat.com>
Subject: Re: [PATCH]sched: fix typo in sched-rt-group.txt file
Date: Tue, 12 May 2009 20:05:06 +0900 [thread overview]
Message-ID: <49b7c2350905120405w3591a92bj265dff000929a928@mail.gmail.com> (raw)
In-Reply-To: <20090512094210.GD32292@elte.hu>
2009/5/12 Ingo Molnar <mingo@elte.hu>:
>
> * Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
>
>> On Tue, 2009-05-12 at 17:37 +0900, GeunSik Lim wrote:
>> >
>> >
>> > 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.
>>
>> > commit d6af702008117ca489a2f5476239d1688a517e98
>> > Author: GeunSik,Lim <leemgs1@gmail.com>
>> > 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
>> >
>> > Signed-off-by: GeunSik Lim <geunsik.lim@samsung.com>
>> >
>> > diff --git a/Documentation/scheduler/sched-rt-group.txt b/Documentation/scheduler/sched-rt-group.txt
>> > index 5ba4d3f..1537146 100644
>> > --- a/Documentation/scheduler/sched-rt-group.txt
>> > +++ b/Documentation/scheduler/sched-rt-group.txt
>> > @@ -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
>
> 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
>
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?
--
Regards,
GeunSik Lim
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" 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/
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-05-12 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 8:37 [PATCH]sched: fix typo in sched-rt-group.txt file GeunSik Lim
2009-05-12 9:15 ` Peter Zijlstra
2009-05-12 9:42 ` Ingo Molnar
2009-05-12 11:05 ` GeunSik Lim [this message]
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=49b7c2350905120405w3591a92bj265dff000929a928@mail.gmail.com \
--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=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).