[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111017124647.GA12838@srcf.ucam.org>
Date: Mon, 17 Oct 2011 13:46:47 +0100
From: Matthew Garrett <mjg@...hat.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Peter Zijlstra <peterz@...radead.org>,
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, Oct 17, 2011 at 11:38:03AM +0200, Thomas Gleixner wrote:
> Unfortunately this is a full speed rolling trainwreck already. The
> whole app space is made to encourage shitty applications. Android is
> designed exactly in that way and it seems that all other desktop folks
> have fully adopted that adsurdity.
>
> Back when NOHZ was merged in the kernel, powertop made people fix crap
> left and right in not time. Why should we add something which actively
> fosters crappy applications today?
They're orthogonal. Sometimes you want timer-driven behaviour (how else
are you going to draw animations?) and that's obviously going to
generate wakeups. This is for the idle case, where the user is no longer
sitting in front of the machine but you don't want to trigger a full
system suspend. We either need every application that ever uses
timer-driven behaviour to support setting its own timer slack on some
sort of external policy decision, or we need a way to let the kernel
force them to.
--
Matthew Garrett | mjg59@...f.ucam.org
--
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