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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 14 Nov 2006 01:27:19 -0500
From:	Len Brown <>
To:	Andreas Mohr <>
Cc:	Thomas Gleixner <>, Ingo Molnar <>,
Subject: Re: CONFIG_NO_HZ: missed ticks, stall (keyb IRQ required) [2.6.18-rc4-mm1]

> > > > > How useful would it be to simply disable C2 operation (but not C1)
> > > > > in CONFIG_NO_HZ mode after's been determined to kill APIC timer?:
> > 
> > If the goal is saving power, then disabling dynticks will likely
> > be more attractive than disabling C2.  Perhaps you can measure it?

> (Conrad EKM 265, to be precise).

> The results are (waited for values to settle down each time):
> -dyntick4, C1, CONFIG_NO_HZ:
>      83.9W KDE idle, 95.2W bash while 1
> -dyntick4, C2 (C1-only hack disabled, kernel rebuilt), CONFIG_NO_HZ off:
>      84.4W KDE idle, 95.4W bash while 1
> -dyntick4, acpi=off (i.e. APM active), -dynticks:
>      85.5W KDE idle, 95.5W bash while 1
> Bet you didn't see this coming...
> Again, this is Athlon 1200 *desktop*, with some EPOX VIA motherboard
> ("8K5A3+" ??).

Yes, I assumed you were running on a laptop...

These three measurements tell me that there is no significant
power savings difference between these configurations on this system.

One has to wonder why the hardware vendor supports C2 on this box,
as its sole function seems  to be to break the local APIC timer...

BTW. when I've had to measure small idle power differences, I've found
variance is smaller when I run at init 1.

> > But this is even more true when talking about C3 -- it certainly saves more
> > power than dynticks does.  This is true for the example system here:
> >
> > 
> > So given that C3 on every known system that has shipped to date
> > breaks the LAPIC timer (and apparently this applies to C2 on these AMD boxes),
> > dynticks needs a solid story for co-existing with C3.
> Indeed, we need a good and flexible fallback mechanism.
> However I would slightly slant dynticks towards being active even in cases
> where it actually happens to consume *slightly* more power due to C2 disabled,
> since it *seems* that CPU load is lower with dynticks
> (less timer background load) / desktop timing is slightly more precise.
> And we all want fast desktops that are waaaaay better than XP, right?

I don't expect dynticks to save significant power on the desktop.
(5-10% would be significant, 1% is not significant)
I do expect dynticks to reduce the load on un-modified virtual guest OSs.
I do expect dynticks it to reduce power on highly power managed mobile systems.

I believe that either #2 or #3 by themselves justify deploying dynticks.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists