On Tue, Jun 29, 2010 at 11:57:00PM -0400, Ted Unangst wrote:
> Here's a first cut at throwing some code into the kernel. You'll
> definitely want to kill apmd if you're running it. It's rather rough, in
> the wrong spot, and so on, but it's a place to start for further hacking.
> I'm not conv
The current situation where apmd monitors system load and adjusts the
hw.setperf sysctl has a number of flaws. While it's nice to keep the
policy outside the kernel and allow tuning, the polling interval is too
slow to be responsive. More aggressive polling intervals and we end up
affecting t
