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

Date:	Thu, 30 Apr 2009 11:24:24 -0700
From:	Alok Kataria <akataria@...are.com>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	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


On Mon, 2009-04-27 at 16:07 -0700, Alok Kataria wrote:
> 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
> 
Ingo/Thomas,

I noticed that the default HZ value was switched back to 1000 (from 250)
about an year back. The commit log didn't have any details about the
switch, and I was wondering what prompted that change ?

-------------------------------------------------------------------------
commit 5cb04df8d3f03e37a19f2502591a84156be71772
    x86: defconfig updates

    refresh 32-bit defconfig too, and update the 64-bit configs as well,
    the defconfig should be much more useful by default, so most of the
    updates are the enabling of various options.
-------------------------------------------------------------------------

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/