Re: [patch 00/43] ktimer reworked

[Christoph Hellwig]

On Thu, Dec 01, 2005 at 05:13:17PM -0500, Kyle Moffett wrote:
> In this patch there are two ways of setting up code to run at some  
> point in the future: timers and timeouts.
> 
> A timeout (like waiting for somebody to answer the phone) is  
> optimized to never happen (they will hopefully pick up first).  If  
> everything works perfectly; it will be stopped before it has a chance  
> to go off.
> 
> A timer (like a kitchen timer telling you the cookies are done) is  
> optimized to be added and sit around until it expires.  You just  
> don't turn off the timer and take the cookies out before they are done.

Heh, in my dumb non-native speaker mind I'd expectit the other way around,
as in a timeout is expected to time out :)  and a timer is expect to happen,
as in say the timer the tells you your breakfast egg is ready.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/