Hi!
> > No, that's fine, we already have to call it before entering the PM
> > state, so I'll just pass it along and, at the low level, decide how
> > deep to sleep based on that.
> >
> > I think I should also add some stats on the amount of interrupts, since
> > it would be fairly inefficient to keep entering deep PM state on a
> > machine with typically little timer interrupts but high HW interrupt
> > (Rusty mentions case of packet forwarding routers or that kind of thing)
>
> Maybe some HW timer interrupt mask could be used? Also it would be
> nice to check for file IO.
Well, you could mask those interrupts, but it would ruin your
packet-forwarding performance, so you probably do not want to do
that...
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
