linux-kernel - Re: [PATCH] x86: Reduce the default HZ value

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]

Message-ID: <20090507221628.GI6377@localdomain>
Date:	Thu, 7 May 2009 15:16:28 -0700
From:	Ravikiran G Thirumalai <kiran@...lex86.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Chris Snook <chris.snook@...il.com>, akataria@...are.com,
	"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	the arch/x86 maintainers <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: Reduce the default HZ value

On Thu, May 07, 2009 at 09:34:03PM +0100, Alan Cox wrote:
>> >> Given your use case, what you really need to do is get Red Hat,
>> >> Novell, et al. on the phone and ask them to ship kernels with HZ=100,
>> >> because the distributions do their own thing anyway.
>
>As a side note Red Hat ships runtime configurable tick behavior in RHEL
>these days. HZ is fixed but the ticks can be bunched up. That was done as
>a quick fix to keep stuff portable but its a lot more sensible than
>randomly messing with the HZ value and its not much code either.
>

That's interesting!
Could you please point us to the patch if you can?

(As a HPC + virtualization shop, we set HZ to 100 all the time,
and a patch like the one you mention above sounds great)

Thanks,
Kiran

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