[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4C15F9D0.40706@kernel.org>
Date: Mon, 14 Jun 2010 11:43:44 +0200
From: Tejun Heo <tj@...nel.org>
To: Jiri Slaby <jirislaby@...il.com>
CC: mingo@...e.hu, tglx@...utronix.de, bphilips@...e.de,
yinghai@...nel.org, akpm@...ux-foundation.org,
torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
jeff@...zik.org, linux-ide@...r.kernel.org,
stern@...land.harvard.edu, gregkh@...e.de, khali@...ux-fr.org
Subject: Re: [PATCH 09/12] irq: implement IRQ expecting
Hello,
On 06/14/2010 11:21 AM, Jiri Slaby wrote:
> On 06/13/2010 05:31 PM, Tejun Heo wrote:
>> --- a/kernel/irq/spurious.c
>> +++ b/kernel/irq/spurious.c
> ...
>
>> @@ -25,9 +26,43 @@ enum {
>> /* IRQ polling common parameters */
>> IRQ_POLL_SLOW_INTV = 3 * HZ, /* not too slow for ppl, slow enough for machine */
>> IRQ_POLL_INTV = HZ / 100, /* from the good ol' 100HZ tick */
>> + IRQ_POLL_QUICK_INTV = HZ / 1000, /* pretty quick but not too taxing */
>>
>> IRQ_POLL_SLOW_SLACK = HZ,
>> IRQ_POLL_SLACK = HZ / 1000, /* 10% slack */
>> + IRQ_POLL_QUICK_SLACK = HZ / 10000, /* 10% slack */
>
> Hi. These are zeros on most systems (assuming distros set HZ=100 and
> 250), what is their purpose then?
On every tick and no slack. :-)
--
tejun
--
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/
Powered by blists - more mailing lists