[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1005151716180.24645-100000@netrider.rowland.org>
Date: Sat, 15 May 2010 17:19:55 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: Brian Swetland <swetland@...gle.com>
cc: Kevin Hilman <khilman@...prootsystems.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Tony Lindgren <tony@...mide.com>,
Matthew Garrett <mjg@...hat.com>,
Paul Walmsley <paul@...an.com>,
Arve Hjønnevåg <arve@...roid.com>,
Linux-pm mailing list <linux-pm@...ts.linux-foundation.org>,
Kernel development list <linux-kernel@...r.kernel.org>,
Tejun Heo <tj@...nel.org>, Oleg Nesterov <oleg@...hat.com>,
<magnus.damm@...il.com>, Theodore Ts'o <tytso@....edu>,
mark gross <mgross@...ux.intel.com>,
Arjan van de Ven <arjan@...radead.org>,
Geoff Smith <geoffx.smith@...el.com>,
Benoît Cousson <b-cousson@...com>,
<linux-omap@...r.kernel.org>, Vitaly Wool <vitalywool@...il.com>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>,
Liam Girdwood <lrg@...mlogic.co.uk>
Subject: Re: [linux-pm] [PATCH 0/8] Suspend block api (version 6)
On Fri, 14 May 2010, Brian Swetland wrote:
> In tickless mode, the time until next timer is a signed int, so the
> longest the kernel will ever sleep is ~2 seconds at a go. In
> practice, userspace entities often have polling behavior that can
> trigger more often than that, and I've observed some kernel periodic
> timers (haven't cataloged them recently) that happen more often than
> once a second.
Paul and Kevin, how does the OMAP implementation handle these
difficulties?
Also, how does it handle the issue of ill-behaved apps?
Alan Stern
--
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