[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100527210609.GA8865@srcf.ucam.org>
Date: Thu, 27 May 2010 22:06:09 +0100
From: Matthew Garrett <mjg59@...f.ucam.org>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Arve Hjønnevåg <arve@...roid.com>,
Florian Mickler <florian@...kler.org>,
Vitaly Wool <vitalywool@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Paul@...p1.linux-foundation.org, felipe.balbi@...ia.com,
Linux OMAP Mailing List <linux-omap@...r.kernel.org>,
Linux PM <linux-pm@...ts.linux-foundation.org>
Subject: Re: [linux-pm] [PATCH 0/8] Suspend block api (version 8)
On Thu, May 27, 2010 at 10:03:14PM +0100, Alan Cox wrote:
> On Thu, 27 May 2010 18:59:20 +0100
> Matthew Garrett <mjg59@...f.ucam.org> wrote:
> > Ok. So the existing badly-behaved application ignores your request and
> > then gets blocked. And now it no longer responds to wakeup events. So
> > you penalise well-behaved applications without providing any benefits to
> > badly-behaved ones.
>
> I don't see how you put the first two sentences together and get the
> final one.
>
> When you beat up badly behaved apps that doesn't penalise well behaved
> ones.
If you're going to block an app on drawing then you either need to
reenable drawing on wakeup or you need to have an interface for alerting
the app to the fact that drawing is about to block and it should get
back to its event loop. The first is suboptimal, the second penalises
well behaved apps.
--
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