x86: Reduce the default HZ value
Quoted 11 lines
Quoted 10 lines
Quoted 5 lines
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_dividerpatch ?
And that's still same as reducing the HZ value only that it can be done dynamically (boot time), right ?
Quoted 7 lines
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
Quoted 16 lines · On Tue, 2009-05-12 at 12:45 -0700, [email protected] wrote:
Quoted 16 lines
Quoted 10 lines
Quoted 5 lines
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_dividerpatch ?
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.
Quoted 4 lines
Quoted 2 lines
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?
I think it is because during the time when this was implemented for RHEL 5, mainline was moving towards the tickless approach, which might have prompted people to think that it would no more be useful for mainline.
Since Alan was the one who implemented those patches, I guess he would have a better say on this. Alan, are there any plans for mainlining this now ?
Alok
Quoted 9 lines
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