[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20061024035346.GA24538@srcf.ucam.org>
Date: Tue, 24 Oct 2006 04:53:46 +0100
From: Matthew Garrett <mjg59@...f.ucam.org>
To: Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc: Shem Multinymous <multinymous@...il.com>,
David Zeuthen <davidz@...hat.com>,
David Woodhouse <dwmw2@...radead.org>,
linux-kernel@...r.kernel.org, olpc-dev@...top.org, greg@...ah.com,
len.brown@...el.com, sfr@...b.auug.org.au
Subject: Re: Battery class driver.
On Tue, Oct 24, 2006 at 01:48:27PM +1000, Benjamin Herrenschmidt wrote:
> On Tue, 2006-10-24 at 04:27 +0100, Matthew Garrett wrote:
> > Reading the battery status has the potential to call an SMI that might
> > take an arbitrary period of time to return, and we found that having
> > querying at around the 1 second mark tended to result in noticable
> > system performace degredation.
> I think it's up to the backend to poll more slowly and cache the results
> on those machines then.
The kernel backend or the userspace backend? We need to decide on
terminology :) There's no good programmatic way of determining how long
a query will take other than doing it and looking at the result. I guess
we could do that at boot time.
--
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