[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100602125811.4ae414e2@lxorguk.ukuu.org.uk>
Date: Wed, 2 Jun 2010 12:58:11 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Arve Hjønnevåg
<arve@...roid.com>, "Rafael J. Wysocki" <rjw@...k.pl>,
Florian Mickler <florian@...kler.org>,
Matthew Garrett <mjg59@...f.ucam.org>,
Alan Stern <stern@...land.harvard.edu>,
Paul@...p1.linux-foundation.org,
LKML <linux-kernel@...r.kernel.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 Wed, 02 Jun 2010 11:10:51 +0200
Peter Zijlstra <peterz@...radead.org> wrote:
> On Wed, 2010-06-02 at 10:29 +0200, Thomas Gleixner wrote:
>
>
> > If I understood you correctly then you can shutdown the CPU in idle
> > completelty already, but that's not enough due to:
> >
> > 1) crappy applications keeping the cpu away from idle
> > 2) timers firing
> >
> > Would solving those two issues be sufficient for you or am I missing
> > something ?
>
> Aren't the container snapshot/resume people fighting the same set of
> problems here?
And virtualisation - its a big one for virtualisation because if you've
got 1000 misbehaving guests generating 100 wakeups a second you've got a
problem ....
Alan
--
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