[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1318869239.4172.64.camel@twins>
Date: Mon, 17 Oct 2011 18:33:59 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: Matthew Garrett <mjg@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Arjan van de Ven <arjan@...ux.intel.com>,
Lennart Poettering <mzxreary@...inter.de>,
Andrew Morton <akpm@...ux-foundation.org>,
"Kirill A. Shutemov" <kirill@...temov.name>,
Paul Menage <menage@...gle.com>,
Li Zefan <lizf@...fujitsu.com>,
containers@...ts.linux-foundation.org,
jacob.jun.pan@...ux.intel.com, linux-kernel@...r.kernel.org,
Matt Helsley <matthltc@...ibm.com>, linux-api@...r.kernel.org,
Kay Sievers <kay.sievers@...y.org>, harald@...hat.com,
david@...ar.dk, greg@...ah.com
Subject: Re: [PATCH, v10 3/3] cgroups: introduce timer slack controller
On Mon, 2011-10-17 at 16:48 +0100, Alan Cox wrote:
> > Hard enforcement is very much better than papering over because it makes
> > the individual developer instantly aware that he's got a problem.
>
> Not always
>
> If you do weird container crap with timers than app authors will simply
> point out that the weird container crap is buggy as it works properly in
> a normal environment.
Oh agreed. I never said the hard enforcement would/should rely on
container crap. I'm very much in favour of a machine that's fully
functional with a CGROUP=n kernel, thank you very much.
Sadly a number of (userspace) wankers (some included on this thread)
seem hell bent on making that impossible.
--
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