[lkml]   [2008]   [Apr]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Higer latency with dynamic tick (need for an io-ondemand govenor?)
"Woodruff, Richard" <> writes:

> When capturing some traces with dynamic tick we were noticing the
> interrupt latency seems to go up a good amount. If you look at the trace
> the gpio IRQ is now offset a good amount. Good news I guess is its
> pretty predictable.
> * If we couple this with progressively higher latency C-States we see
> that IO speed can fall by a good amount, especially for PIO mixes. Now
> if QOS is maintained you may or may-not care.
> I was wondering what thoughts of optimizing this might be.
> One thought was if an io-ondemand of some sort was used. It could track
> interrupt statistics and be feed back into cpu-idle. When there is a
> high interrupt load period it could shrink the acceptable latency and
> thus help choose a good a C-State which favors throughput. Some moving
> average window could be used to track it.
> Perhaps a new interrupt attribute could be attached at irq request time
> to allow the tracking of bandwidth important devices.
> The attached is captured on a .22 kernel. The same should be available
> in a bit on a .24 kernel.

Are you talking about x86?

On older x86 this effect should have been handled by the C state
algorithm taking the bus master activity register into account (which
should also trigger for interrupts)

But I think the register has been nop'ed on newer platforms
so indeed we'll need some way to handle this.


 \ /
  Last update: 2008-04-20 14:43    [W:0.072 / U:3.320 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site