On Tue, 2005-01-18 at 21:21 -0800, Tony Lindgren wrote: > * Tony Lindgren <[EMAIL PROTECTED]> [050118 21:08]: > > * Benjamin Herrenschmidt <[EMAIL PROTECTED]> [050118 20:22]: > > > > > > BTW. Is it possible, when entering the "idle" loop, to quickly know an > > > estimate of when the next tick shoud actually kick in ? > > > > Yes, see next_timer_interrupt() for that. > > Hmmm, or maybe you mean _quick_estimate_ instead of > next_timer_interrupt()? > > I don't think there's any faster way to estimate the skippable ticks > without going through the list like next_timer_interrupt already does. > Does anybody have any ideas for that?
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) Ben. - 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/
