Messages in this thread | | | Subject | Re: [PATCH] maximum latency tracking infrastructure (version 3) | From | Arjan van de Ven <> | Date | Mon, 28 Aug 2006 18:48:19 +0200 |
| |
> Another question is how one would do callback processing in idle handler: > one could figure out the idle mode (latency) in advance and *then* call > only all those idle callbacks that have more stringent requirements > than the currently calculated idle mode's latency (and then calculate > the idle mode again based on the current time after all those callbacks??), > or one could just unconditionally call all idle handlers and then figure out > idle length and go to sleep. Which one is better?
I'm not sure about either actually. Well if it's just to refill stuff etc then I would just call all. After all it may save interrupts and early wakeups if you do this, so there's a power advantage to be gained.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |