linux-kernel - Re: [Fwd: Re: RFC for a new Scheduling policy/class in the Linux-kernel]

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]

Message-ID: <1272897682.1642.124.camel@laptop>
Date:	Mon, 03 May 2010 16:41:22 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Ted Baker <baker@...fsu.edu>
Cc:	raj@....cmu.edu, jayhawk@....ucsc.edu, raistlin@...ux.it,
	niehaus@...c.ku.edu, henrik@...tad.us,
	linux-kernel@...r.kernel.org, mingo@...e.hu,
	billh@...ppy.monkey.org, linux-rt-users@...r.kernel.org,
	fabio@...dalf.sssup.it, anderson@...unc.edu, tglx@...utronix.de,
	dhaval.giani@...il.com, cucinotta@...up.it, lipari@...is.sssup.it,
	baker.tlh@...cast.net
Subject: Re: [Fwd: Re: RFC for a new Scheduling policy/class in the
 Linux-kernel]

Hi Ted,

On Mon, 2010-04-26 at 07:56 -0400, Ted Baker wrote:
> I have not seen any more e-mail on this.  How is it going?  Is there any
> chance of rolling in some corrections for the SCHED_SPORADIC treatment?  In
> particular, could we have a DO_NOT_RUN priority, that is guaranteed to
> prevent a task from running at all?

Without having fully read the referenced paper, we're currently looking
to support the sporadic task model through SCHED_DEADLINE (by our SSSUP
friends):

  http://lkml.org/lkml/2010/2/28/107

This work aims to implement a full sporadic task scheduler [initially
(g)EDF], SCHED_SPORADIC would have been a better name, but since POSIX
stole that from us we took SCHED_DEADLINE to indicate its a deadline
scheduler.

Along with this work comes the full Deadline-inheritance (which should
be but a small change from our current Priority-inheritance code), and
also Bandwidth-inheritance (more work). Esp. the latter would also be
required for your proposed SCHED_SPORADIC since it does aim to be a
'strict' bandwidth enforcing scheduler.

[Does the proposed 'fixed' SCHED_SPORADIC deal with admission control?]

But as it stands, this work would provide much more complete sporadic
task support than the fixed SCHED_SPORADIC would.

--
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/