linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: leemgs1@gmail.com, 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 11:42:10 +0200	[thread overview]
Message-ID: <20090512094210.GD32292@elte.hu> (raw)
In-Reply-To: <1242119738.11251.322.camel@twins>


* 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

  reply	other threads:[~2009-05-12  9:42 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 [this message]
2009-05-12 11:05     ` 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=20090512094210.GD32292@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=leemgs1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.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).