linux-kernel - Re: massive_intr on CFS, BFS, and EDF

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: <1253918258.18939.192.camel@laptop>
Date:	Sat, 26 Sep 2009 00:37:38 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Chris Friesen <cfriesen@...tel.com>
Cc:	Michael Trimarchi <trimarchi@...dalf.sssup.it>,
	sat <takeuchi_satoru@...fujitsu.com>,
	lkml <linux-kernel@...r.kernel.org>,
	Con Kolivas <kernel@...ivas.org>, Ingo Molnar <mingo@...e.hu>,
	Raistlin <raistlin@...ux.it>
Subject: Re: massive_intr on CFS, BFS, and EDF

On Fri, 2009-09-25 at 15:31 -0600, Chris Friesen wrote:
> On 09/25/2009 10:07 AM, Michael Trimarchi wrote:
> > It is important to note that
> > the expected behavior of an edf scheduler is *not* a fair one. It has to
> > do its best to guarantee the deadlines of the admitted tasks.
> 
> Do you allow oversubscription with EDF?  It would seem so based on these
> results.  Would it maybe make sense to disallow oversubscription, or
> make it an option?

afaiu he doesn't, he simply splits the task's wcet between parent and
child and (intends?) to feed back on child exit.

> If you have massive oversubscription with EDF, what is the design
> intent?  Do you try to meet the goals on as many tasks as possible,
> while the oversubscribed tasks get nothing?

oversubscribing edf isn't in general recommended, iirc u>1 gives
unbounded latencies with edf.

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