lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 6 Jun 2010 01:16:34 -0700 (PDT) From: david@...g.hm To: Arjan van de Ven <arjan@...radead.org> cc: Linus Torvalds <torvalds@...ux-foundation.org>, Ingo Molnar <mingo@...e.hu>, tytso@....edu, Brian Swetland <swetland@...gle.com>, Neil Brown <neilb@...e.de>, Arve Hj?nnev?g <arve@...roid.com>, Thomas Gleixner <tglx@...utronix.de>, "Rafael J. Wysocki" <rjw@...k.pl>, Alan Stern <stern@...land.harvard.edu>, Felipe Balbi <felipe.balbi@...ia.com>, Peter Zijlstra <peterz@...radead.org>, LKML <linux-kernel@...r.kernel.org>, Florian Mickler <florian@...kler.org>, Linux OMAP Mailing List <linux-omap@...r.kernel.org>, Linux PM <linux-pm@...ts.linux-foundation.org>, Alan Cox <alan@...rguk.ukuu.org.uk>, James Bottomley <James.Bottomley@...e.de>, Peter Zijlstra <a.p.zijlstra@...llo.nl>, Kevin Hilman <khilman@...prootsystems.com>, "H. Peter Anvin" <hpa@...or.com> Subject: Re: suspend blockers & Android integration On Thu, 3 Jun 2010, Arjan van de Ven wrote: > On Thu, 3 Jun 2010 19:26:50 -0700 (PDT) > Linus Torvalds <torvalds@...ux-foundation.org> wrote: > >> >> If the system is idle (or almost idle) for long times, I would >> heartily recommend actively shutting down unused cores. Some CPU's >> are hopefully smart enough to not even need that kind of software >> management, but I suspect even the really smart ones might be able to >> take advantage of the kernel saying: "I'm shutting you down, you >> don't have to worry about latency AT ALL, because I'm keeping another >> CPU active to do any real work". > > sadly the reality is that "offline" is actually the same as "deepest C > state". At best. > > As far as I can see, this is at least true for all Intel and AMD cpus. > > And because there's then no power saving (but a performance cost), it's > actually a negative for battery life/total energy. I believe that this assumes you are in the 'race to idle' situation where when you finish your work you can shutdown. If the work is ongoing you may never shutdown. Also, what about the new CPUs where you can ramp up the clockspeed on some cores if you hsut down other cores? that couls also benifit individual threads. David Lang -- 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