|| ||Peter Zijlstra <peterz-AT-infradead.org> |
|| ||Alan Cox <alan-AT-lxorguk.ukuu.org.uk> |
|| ||Re: [linux-pm] [PATCH 0/8] Suspend block api (version 8) |
|| ||Fri, 28 May 2010 15:20:17 +0200|
|| ||Arve HjÃ¸nnevÃ¥g <arve-AT-android.com>,
Matthew Garrett <mjg59-AT-srcf.ucam.org>,
Alan Stern <stern-AT-rowland.harvard.edu>,
Thomas Gleixner <tglx-AT-linutronix.de>,
Florian Mickler <florian-AT-mickler.org>, felipe.balbi-AT-nokia.com,
Linux OMAP Mailing List <linux-omap-AT-vger.kernel.org>,
Linux PM <linux-pm-AT-lists.linux-foundation.org>|
|| ||Article, Thread
On Fri, 2010-05-28 at 14:02 +0100, Alan Cox wrote:
> On Fri, 28 May 2010 14:30:36 +0200
> Peter Zijlstra <firstname.lastname@example.org> wrote:
> > On Fri, 2010-05-28 at 13:21 +0100, Alan Cox wrote:
> > > [Total kernel changes
> > >
> > > Ability to mark/unmark a scheduler control group as outside of
> > > some parts of idle consideration. Generically useful and
> > > localised. Group latency will do most jobs fine (Zygo is correct
> > > it can't solve his backup case elegantly I think)
> > >
> > > Test in the idling logic to distinguish the case and only needed
> > > for a single Android specific power module. Generically useful
> > > and localised]
> > I really don't like this..
> > Why can't we go with the previously suggested: make bad apps block on
> > QoS resources or send SIGXCPU, SIGSTOP, SIGTERM and eventually SIGKILL
> Ok. Are you happy with the QoS being attached to a scheduler control
> group and the use of them to figure out what is what ?
Up to a point, but explicitly not running runnable tasks complicates the
task model significantly, and interacts with fun stuff like bandwidth
inheritance and priority/deadline inheritance like things -- a subject
you really don't want to complicate further.
We really want to do our utmost best to make applications block on
something without altering our task model.
If applications keep running despite being told repeatedly to cease, I
think the SIGKILL option is a sane one (they got SIGXCPU, SIGSTOP and
SIGTERM before that) and got ample opportunity to block on something.
Traditional cpu resource management treats the CPU as an ever
replenished resource, breaking that assumption (not running runnable
tasks) puts us on very shaky ground indeed.
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
to post comments)