lkml.org 
[lkml]   [2006]   [Jun]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    Date
    From
    SubjectRe: [ckpatch][15/29] hz-no_default_250.patch
    >
    >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.

    diff --fast -Ndpru linux-2.6.17-rc6~/kernel/Kconfig.hz linux-2.6.17-rc6+/kernel/Kconfig.hz
    --- linux-2.6.17-rc6~/kernel/Kconfig.hz 2006-06-06 02:57:02.000000000 +0200
    +++ linux-2.6.17-rc6+/kernel/Kconfig.hz 2006-06-16 17:15:46.884794000 +0200
    @@ -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
    --
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2006-06-18 17:06    [W:0.033 / U:0.656 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site