linux-kernel - Re: periods and deadlines in SCHED

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] [day] [month] [year] [list]

Message-ID: <1280906045.1923.721.camel@laptop>
Date:	Wed, 04 Aug 2010 09:14:05 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Andrea Bastoni <bastoni@...unc.edu>
Cc:	Bjoern Brandenburg <bbb@...il.unc.edu>,
	Raistlin <raistlin@...ux.it>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Song Yuan <song.yuan@...csson.com>,
	Dmitry Adamushko <dmitry.adamushko@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Nicola Manica <nicola.manica@...i.unitn.it>,
	Luca Abeni <lucabe72@...il.it>,
	Claudio Scordino <claudio@...dence.eu.com>,
	Harald Gustafsson <harald.gustafsson@...csson.com>,
	Giuseppe Lipari <lipari@...is.sssup.it>
Subject: Re: periods and deadlines in SCHED_DEADLINE

On Tue, 2010-08-03 at 23:52 -0400, Andrea Bastoni wrote:
> Instead, if you want to use the cpuset + affinity to define possibly _overlapping_ clusters (or
> containers, or servers) to support different budgets on each CPU (something similar to cgroup,
> see [1,3]), forcing only two configuration (single cpu/full cluster) may be restrictive. 

cpusets doesn't allow overlapping load-balance domains as it stands
today. In that case it would end up being a single large domain.

With cpu affinity we can of course create whatever we want, hence my
suggestion to limit allowed affinity masks to 1 cpu or the full
load-balance domain.
--
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/