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
| ||
|
Date: Mon, 28 Dec 2009 15:51:12 +0100 From: Peter Zijlstra <peterz@...radead.org> To: Raistlin <raistlin@...ux.it> Cc: linux-kernel <linux-kernel@...r.kernel.org>, michael trimarchi <michael@...dence.eu.com>, Fabio Checconi <fabio@...dalf.sssup.it>, Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>, Dhaval Giani <dhaval.giani@...il.com>, Johan Eker <johan.eker@...csson.com>, "p.faure" <p.faure@...tech.ch>, Chris Friesen <cfriesen@...tel.com>, Steven Rostedt <rostedt@...dmis.org>, Henrik Austad <henrik@...tad.us>, Frederic Weisbecker <fweisbec@...il.com>, Darren Hart <darren@...art.com>, Sven-Thorsten Dietrich <sven@...bigcorporation.com>, Bjoern Brandenburg <bbb@...unc.edu>, Tommaso Cucinotta <tommaso.cucinotta@...up.it>, "giuseppe.lipari" <giuseppe.lipari@...up.it>, Juri Lelli <juri.lelli@...il.com> Subject: Re: [RFC 10/12][PATCH] SCHED_DEADLINE: group bandwidth management code On Fri, 2009-10-16 at 17:46 +0200, Raistlin wrote: > CPU Container Groups support for SCHED_DEADLINE is introduced by this commit. > > CGroups, if configured, have a SCHED_DEADLINE bandwidth, and it is enforced > that the sum of the bandwidths of entities (tasks and groups) belonging to > a group stays below its own bandwidth. No real comment on the code here, but since we have a deadline bandwidth reservation, should we not also couple to the existing rt (fifo) bandwidth reservation? We can't after all guarantee the FIFO time if there's deadline reservations around for more. -- 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/
Powered by blists - more mailing lists