linux-kernel - Re: [PATCH]sched: fix typo in sched-rt-group.txt file

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 12 May 2009 11:15:38 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	leemgs1@...il.com
Cc:	Ingo Molnar <mingo@...e.hu>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-rt-users <linux-rt-users@...r.kernel.org>,
	tglx <tglx@...utronix.de>, williams <williams@...hat.com>
Subject: Re: [PATCH]sched: fix typo in sched-rt-group.txt file

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@...il.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@...sung.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
>  do deadline inheritance (since priority is inversely proportional to the
>  deadline delta (deadline - now).
>  
> 
> 
> -----------------------------------------------
> To unsubscribe from this list: send the line "unsubscribe linux-***" 
> in the body of a message to majordomo@...r.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@...sung.com
>          2) leemgs@...il.com , leemgs1@...il.com
> HomePage: http://intomail.dnip.net/invain/me/
> -----------------------------------------------

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/