hz-no_default_250.patch
PATCH 15/29 hz-no_default_250.patch
Make 250 HZ a value that is not selected by default and give some better recommendations in help.
kernel/Kconfig.hz | 15 +++++++++------ 1 files changed, 9 insertions(+), 6 deletions(-)
kernel/Kconfig.hz +9 -6
@@ -21,14 +21,17 @@ choice help 100 HZ is a typical choice for servers, SMP and NUMA systems with lots of processors that may show reduced performance if - too many timer interrupts are occurring. + too many timer interrupts are occurring. Laptops may also show + improved battery life. - config HZ_250 + config HZ_250_NODEFAULT bool "250 HZ" help - 250 HZ is a good compromise choice allowing server performance - while also showing good interactive responsiveness even - on SMP and NUMA systems. + 250 HZ is a lousy compromise choice allowing server interactivity + while also showing desktop throughput and no extra power saving on + laptops. Good for when you can't make up your mind. + + Recommend 100 or 1000 instead. config HZ_1000 bool "1000 HZ"
@@ -41,6 +44,6 @@ endchoice config HZ int default 100 if HZ_100 - default 250 if HZ_250 + default 250 if HZ_250_NODEFAULT default 1000 if HZ_1000
Signature · 1 line
-ck
Hi Con,
Quoted 22 lines · Con Kolivas
Make 250 HZ a value that is not selected by default and give some better recommendations in help.
Signed-off-by Con Kolivas <[email protected]>kernel/Kconfig.hz | 15 +++++++++------ 1 files changed, 9 insertions(+), 6 deletions(-)Index: linux-ck-dev/kernel/Kconfig.hz
===================================================================kernel/Kconfig.hz +3
-2@@ -21,14 +21,17 @@ choice help 100 HZ is a typical choice for servers, SMP and NUMA systems with lots of processors that may show reduced performance if - too many timer interrupts are occurring. + too many timer interrupts are occurring. Laptops may also show + improved battery life. - config HZ_250 + config HZ_250_NODEFAULT
kernel/Kconfig.hz choice · line 34
Quoted 10 lines
kernel/Kconfig.hz +5
-3bool "250 HZ" help - 250 HZ is a good compromise choice allowing server performance - while also showing good interactive responsiveness even - on SMP and NUMA systems. + 250 HZ is a lousy compromise choice allowing server interactivity + while also showing desktop throughput and no extra power saving on + laptops. Good for when you can't make up your mind. + + Recommend 100 or 1000 instead.
In fact, I use this value (250 Hz) on servers because it provides slightly finer scheduling precision than 100 Hz without the performance impact of 1000 Hz. It also has the advantage that conversions between ms<->jiffies are performed by bit shifts only and no divide nor multiply. I really do not notice any performance hit between 100 and 250 Hz, while I do between 250 and 1000.
Cheers,
Willy
Quoted 34 lines · Willy Tarreau
Hi Con,
Quoted 31 lines · Con Kolivas
Make 250 HZ a value that is not selected by default and give some better recommendations in help.
Signed-off-by Con Kolivas <[email protected]>kernel/Kconfig.hz | 15 +++++++++------ 1 files changed, 9 insertions(+), 6 deletions(-)Index: linux-ck-dev/kernel/Kconfig.hz
===================================================================
--- linux-ck-dev.orig/kernel/Kconfig.hz 2006-06-18 15:23:58.000000000
+1000 +++ linux-ck-dev/kernel/Kconfig.hz 2006-06-18 15:24:28.000000000
+1000 @@ -21,14 +21,17 @@ choicekernel/Kconfig.hz +7
-5help 100 HZ is a typical choice for servers, SMP and NUMA systems with lots of processors that may show reduced performance if - too many timer interrupts are occurring. + too many timer interrupts are occurring. Laptops may also show + improved battery life. - config HZ_250 + config HZ_250_NODEFAULT bool "250 HZ" help - 250 HZ is a good compromise choice allowing server performance - while also showing good interactive responsiveness even - on SMP and NUMA systems. + 250 HZ is a lousy compromise choice allowing server interactivity + while also showing desktop throughput and no extra power saving on + laptops. Good for when you can't make up your mind. +
Quoted 8 lines
kernel/Kconfig.hz choice · line 34
Quoted 1 line
kernel/Kconfig.hz +1
-0+ Recommend 100 or 1000 instead.In fact, I use this value (250 Hz) on servers because it provides slightly finer scheduling precision than 100 Hz without the performance impact of 1000 Hz. It also has the advantage that conversions between ms<->jiffies are performed by bit shifts only and no divide nor multiply. I really do not notice any performance hit between 100 and 250 Hz, while I do between 250 and 1000.
Thanks for your perspective. I found performance hits on computational tasks with 250 vs 100 but your finer precision makes perfect sense.
Signature · 1 line
-ck
Quoted 4 lines
Thanks for your perspective. I found performance hits on computational tasks with 250 vs 100 but your finer precision makes perfect sense.
Or this one so every user can set any value s/he wants. :)
Done-by: Me.
kernel/Kconfig.hz +20 -39
@@ -2,45 +2,26 @@ # Timer Interrupt Frequency Configuration # -choice - prompt "Timer frequency" - default HZ_250 - help - Allows the configuration of the timer frequency. It is customary - to have the timer interrupt run at 1000 HZ but 100 HZ may be more - beneficial for servers and NUMA systems that do not need to have - a fast response for user interaction and that may experience bus - contention and cacheline bounces as a result of timer interrupts. - Note that the timer interrupt occurs on each processor in an SMP - environment leading to NR_CPUS * HZ number of timer interrupts - per second. - - - config HZ_100 - bool "100 HZ" - help - 100 HZ is a typical choice for servers, SMP and NUMA systems - with lots of processors that may show reduced performance if - too many timer interrupts are occurring. - - config HZ_250 - bool "250 HZ" - help - 250 HZ is a good compromise choice allowing server performance - while also showing good interactive responsiveness even - on SMP and NUMA systems. - - config HZ_1000 - bool "1000 HZ" - help - 1000 HZ is the preferred choice for desktop systems and other - systems requiring fast interactive responses to events. +config HZ + int "Timer frequency" + default 100 + ---help--- + Allows the configuration of the timer frequency. It is + customary to have the timer interrupt run at 1000 HZ but 100 HZ + may be more beneficial for servers and NUMA systems that do not + need to have a fast response for user interaction and that may + experience bus contention and cacheline bounces as a result of + timer interrupts. Note that the timer interrupt occurs on each + processor in an SMP environment leading to NR_CPUS * HZ number + of timer interrupts per second. -endchoice + 100 HZ is a typical choice for servers, SMP and NUMA systems + with lots of processors that may show reduced performance if + too many timer interrupts are occurring. -config HZ - int - default 100 if HZ_100 - default 250 if HZ_250 - default 1000 if HZ_1000 + 250 HZ is a good compromise choice allowing server performance + while also showing good interactive responsiveness even on SMP + and NUMA systems. + 1000 HZ is the preferred choice for desktop systems and other + systems requiring fast interactive responses to events.
#<<eof>>
Jan Engelhardt