linux-kernel - Re: Default HZ value for X86

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 30 Apr 2009 19:27:50 +0200
From:	Artur Skawina <art.08.09@...il.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	akataria@...are.com, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>,
	the arch/x86 maintainers <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Default HZ value for X86

Alan Cox wrote:
> On Mon, 27 Apr 2009 16:07:10 -0700
> Alok Kataria <akataria@...are.com> wrote:
>>
>> 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 timers.
> 
> With the tickless kernel does this really matter any more ? We might as

It didn't matter much, until the kernel stopped actually being tickless.
These days, w/ ints on when nonidle, it probably does again...

> well keep a logical 1000 for convenience and accuracy.

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