[lkml]   [2001]   [Oct]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [announce] [patch] limiting IRQ load, irq-rewrite-2.4.11-B5

    On Thu, 4 Oct 2001, BALBIR SINGH wrote:

    > Ingo, is it possible to provide an interface (optional interface) to
    > drivers, so that they can decide how many interrupts are too much.

    well, it existed, and i can add it back - i dont have any strong feelings

    > Drivers who feel that they should go in for interrupt mitigation have
    > the option of deciding to go for it.

    in those cases the 'irq overload' code should not trigger. It's not the
    rate of interrupts that matters, it's the amount of time we spend in irq
    contexts. The code counts the number of times we 'interrupt and interrupt
    context'. Interrupting an irq-context is a sign of irq overload. The code
    goes into 'overload mode' (and disables that particular interrupt source
    for the rest of the current timer tick) only if more than 97% of all
    interrupts from that source 'interrupt and irq context'. (ie. irq load is
    really high.) As any statistical method it has some inaccuracy, but
    'statistically' it gets things right.


    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:04    [W:0.021 / U:35.828 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site