[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100802073400.68a6edd7@schatten.dmk.lab>
Date: Mon, 2 Aug 2010 07:34:00 +0200
From: Florian Mickler <florian@...kler.org>
To: Arjan van de Ven <arjan@...radead.org>
Cc: paulmck@...ux.vnet.ibm.com, "Ted Ts'o" <tytso@....edu>,
linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
arve@...roid.com, mjg59@...f.ucam.org, pavel@....cz, rjw@...k.pl,
stern@...land.harvard.edu, swetland@...gle.com,
peterz@...radead.org, tglx@...utronix.de, alan@...rguk.ukuu.org.uk
Subject: Re: Attempted summary of suspend-blockers LKML thread
Hi,
On Sun, 1 Aug 2010 21:05:48 -0700
Arjan van de Ven <arjan@...radead.org> wrote:
> I'm a little worried that this whole "I need to block suspend" is
> temporary. Yes today there is silicon from ARM and Intel where suspend
> is a heavy operation, yet at the same time it's not all THAT heavy
> anymore.... at least on the Intel side it's good enough to use pretty
> much all the time (when the screen is off for now, but that's a memory
> controller issue more than anything else). I'm pretty sure the ARM guys
> will not be far behind.
I think that the only thing that really matters (longterm) with suspend
is that processes don't get scheduled anymore when the system is
suspended.
Cheers,
Flo
--
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