[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <758575.48890.qm@web180307.mail.gq1.yahoo.com>
Date: Thu, 20 May 2010 16:08:49 -0700 (PDT)
From: David Brownell <david-b@...bell.net>
To: me@...ipebalbi.com
Cc: felipe.balbi@...ia.com, Vladimir Pantelic <pan@...tu-darmstadt.de>,
Matthew Garrett <mjg@...hat.com>,
"me@...ipebalbi.com" <me@...ipebalbi.com>,
Theodore Ts'o <tytso@....edu>,
Brian Swetland <swetland@...gle.com>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>,
Geoff Smith <geoffx.smith@...el.com>,
Kernel development list <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Oleg Nesterov <oleg@...hat.com>, Tejun Heo <tj@...nel.org>,
Linux-pm mailing list <linux-pm@...ts.linux-foundation.org>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
Liam Girdwood <lrg@...mlogic.co.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
Arjan van de Ven <arjan@...radead.org>
Subject: Re: [linux-pm] [PATCH 0/8] Suspend block api (version 6)
> -0700, David Brownell wrote:
> > Some apps do abuse kernel mechanisms, and whether the
> bug is in the
> > app or that kernel mechanism can be a judgement
> call. I'd expect to
>
> hey come on, there's no judgement call for an app polling
> every second
> to check battery status or some other status that doesn't
> change that frequently.
Or something as broken as a non-terminating CPU loop ...
Of course not. But if there's a kernel mechanism exposed to
userspace which really sucks down power ... either it's done
correctly and the problem is userspace abusing it, or it's done
wrong so that it's not possible to be used correctly. There are
some things that just cost power, and that cost can't be escaped.
--
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