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

Message-Id: <711906814@web.de>
Date:	Tue, 12 May 2009 21:45:31 +0200
From:	devzero@....de
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Alok Kataria <akataria@...are.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: Reduce the default HZ value

>> > As a side note Red Hat ships runtime configurable tick behaviour 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.
>> > 
>> Hi Alan, 
>> 
>> I guess you are talking about the tick_divider patch ? 
>> And that's still same as reducing the HZ value only that it can be done
>> dynamically (boot time), right ? 
>
>Yes - which has the advantage that you can select different behaviours
>rather than distributions having to build with HZ=1000 either for
>compatibility or responsiveness can still allow users to drop to a lower
>HZ value if doing stuff like HPC.
>
>Basically it removes the need to argue about it at build time and lets
>the user decide.

any reason why this did not reach mainline?
is it because there were issues with clocksource=pit ?

regards
roland

______________________________________________________
GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://movieflat.web.de

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