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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 27 Apr 2009 16:07:10 -0700
From:	Alok Kataria <akataria@...are.com>
To:	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>
Cc:	the arch/x86 maintainers <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Default HZ value for X86

Hi, 

I was wondering why do we still have the default HZ value as 1000 for
the x86 kernels.

arch/x86/configs/i386_defconfig:CONFIG_HZ=1000
arch/x86/configs/x86_64_defconfig:CONFIG_HZ=1000

With the highres timer implementation it was planned to move away from
relying on high timer interrupt frequency for applications requiring
precise high resolution timer's. 

This quote in the timer/hrtimers.txt also mentions that we should be
able to decrease the frequency of the timeout subsystem, which I assume
would mean reducing HZ value.

---------------------------------------------------------------------
"Another potential benefit is that such a separation allows even more
special-purpose optimization of the existing timer wheel for the low
resolution and low precision use cases - once the precision-sensitive
APIs are separated from the timer wheel and are migrated over to
hrtimers. E.g. we could decrease the frequency of the timeout subsystem
from 250 Hz to 100 HZ (or even smaller)."
---------------------------------------------------------------------

So, are there still any concerns that keep us from lowering the default
HZ value down to 250/100 for mainline ? 

Thanks,
Alok

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ