Date: Mon, 17 Mar 2008 20:40:19 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: John Baldwin <jhb@freebsd.org> Cc: Maxim Sobolev <sobomax@freebsd.org>, src-committers@freebsd.org, cvs-all@freebsd.org, cvs-src@freebsd.org Subject: Re: cvs commit: src/sys/i386/cpufreq est.c Message-ID: <5836.1205786419@critter.freebsd.dk> In-Reply-To: Your message of "Mon, 17 Mar 2008 16:35:51 -0400." <200803171635.51748.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200803171635.51748.jhb@freebsd.org>, John Baldwin writes: >Err, actually, it's the other way around. On previous releases the BIOS is >going to set your CPU to a lower speed on boot to save battery (on a laptop >not connected to A/C during boot). John, you are right about laptops, but people with laptops know power management is part of the job. Nobody would ever dream of having to run powerd on a server, in particular not to get _full_ performance. If you can find some way to detect if we are on a server or a laptop, I'm fine with divergent defaults. But given that suspend/resume has barely worked for any new laptop for 18 months, I can't really justify hurting the servers for the laptops on this issue. Please also note that p4tcc.c driver has done the same thing all along, no matter what the bios hat set, it would set 100%. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5836.1205786419>