tech-kern archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: rfc: high-resolution timer framework

On Wed, Aug 06, 2008 at 07:58:44PM +0100, David Laight wrote:
> Typically you send a message and start a timer for the response.
> When the response arrives the timer is cancelled.
> If the timer expires the message is resent.
> That tends to get repeated for EVERY data message.
> If the OS timers don't support that mode of working (efficiently)
> then EVERY such driver has to implement its own timer framework.

That is fine. The question is: do you stop the timer after every message
or do you just keep it running and move it after the next message.
Moving the timer is often cheaper as removing it.

That said, noone suggested to use a system that is inefficient for
common usage. Full ordering of the timers won't be done.


Home | Main Index | Thread Index | Old Index