On Tue, Oct 24, 2006 at 04:56:30AM +0200, Shem Multinymous wrote:
> 30 seconds? I've seen battery applets that poll 1sec intervals (that's
> actually useful when you tweak power saving). And for things like the
> hdaps accelerometer driver, we're at the 50HZ region.
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.
Possibly it would be useful if the kernel could keep track of how long
certain queries take? That would let userspace calibrate itself without
having to worry about whether it was preempted or not.
> You can't require reading battery status to be a root-only operation.
We certainly can. Whether we want to is another matter :) I tend to
agree that moving to a setup that makes it harder for command-line users
to read the battery status would be a regression.
--
Matthew Garrett | [email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
