[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100619130730.36f8d567@infradead.org>
Date: Sat, 19 Jun 2010 13:07:30 -0700
From: Arjan van de Ven <arjan@...radead.org>
To: Andi Kleen <andi@...stfloor.org>
Cc: Tejun Heo <tj@...nel.org>, 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
On Sat, 19 Jun 2010 21:49:37 +0200
Andi Kleen <andi@...stfloor.org> wrote:
> > Here we have the opportunity to get real good information.. we KNOW
> > now an interrupt is coming, and we can even estimate how long it'll
> > be... Even for the first few after a long time, before a pattern
> > emerges.
>
> Ok but I thought the driver would just fill in a single number
> likely. Is that really that good information?
Tejun suggested tracking this per handler, I'm assuming that instead of
the driver passed number
>
> Alternatively each driver would need to implement some dynamic
> estimation algorithm, but that would be just mostly equivalent
> to having it all in the idle governour?
that's the whole point... let the irq layer track this stuff, and
inform the governor. the governor does not know irqs are expected..
with tejun's change, the irq layer at least will.
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
--
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