| 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
| ||
|
Message-ID: <alpine.LFD.2.00.0905272229190.3397@localhost.localdomain> Date: Wed, 27 May 2009 22:32:28 +0200 (CEST) From: Thomas Gleixner <tglx@...utronix.de> To: john stultz <johnstul@...ibm.com> cc: Jon Hunter <jon-hunter@...com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu> Subject: Re: [PATCH 1/2] Dynamic Tick: Prevent clocksource wrapping during idle On Wed, 27 May 2009, john stultz wrote: > > Why do you want to recalculate the whole stuff over and over ? > > > > That computation can be done when the clock source is initialized or > > any fundamental change of the clock parameters happens. > > > > Stick that value into the clocksource struct and just read it out. > > Sigh. > > I was hoping to avoid hanging another bit of junk off of the clocksource > struct. Sure, but buying that 8 bytes with Einsteinian insanity is nuts. > But I guess we could compute that value on registration and keep it > around. Changes to mult could effect things, but should be well within > the 6% safety net we give ourselves. That was my thought as well, but even if we have to go to 12% it's way better than doing repeated nonsense on the way to idle. Thanks, tglx -- 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