From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754379Ab0E1M4h (ORCPT ); Fri, 28 May 2010 08:56:37 -0400 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:43618 "EHLO www.etchedpixels.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751375Ab0E1M4g (ORCPT ); Fri, 28 May 2010 08:56:36 -0400 Date: Fri, 28 May 2010 14:02:36 +0100 From: Alan Cox To: Peter Zijlstra Cc: Arve =?ISO-8859-14?B?SGr4bm5lduVn?= , Matthew Garrett , Alan Stern , Thomas Gleixner , LKML , Florian Mickler , felipe.balbi@nokia.com, Linux OMAP Mailing List , Linux PM Subject: Re: [linux-pm] [PATCH 0/8] Suspend block api (version 8) Message-ID: <20100528140236.3214929e@lxorguk.ukuu.org.uk> In-Reply-To: <1275049836.1645.1.camel@laptop> References: <20100527222514.0a1710bf@lxorguk.ukuu.org.uk> <20100527230806.4deb6de3@lxorguk.ukuu.org.uk> <20100527220949.GB10602@srcf.ucam.org> <20100527232357.6d14fdb2@lxorguk.ukuu.org.uk> <20100528101755.7b5f6b8a@lxorguk.ukuu.org.uk> <20100528132138.2d802d77@lxorguk.ukuu.org.uk> <1275049836.1645.1.camel@laptop> X-Mailer: Claws Mail 3.7.5 (GTK+ 2.18.9; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 28 May 2010 14:30:36 +0200 Peter Zijlstra 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 ?