[lkml]   [2005]   [Aug]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: FW: [RFC] A more general timeout specification
Joe Korty wrote:

> The returned timeout struct has a bit used to mark the value as absolute. Thus
> the caller treats the returned timeout as a opaque cookie that can be
> reapplied to the next (or more likely, the to-be restarted) timeout.

Okay, endtime is always absolute value of when it should have expired.
But I think I see a problem with the opaque cookie scheme and repeating

Suppose I want to wake my application at INTERVAL nanoseconds from now
on the MONOTONIC clock, then again every INTERVAL nanoseconds after that.

How do I do that with this API?

I can get the first sleep. Suppose I oversleep by X nanoseconds. I
wake, and get an opaque timeout back. How do I ask for the new wake
time to be "endtime + INTERVAL"?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-09-01 00:09    [W:0.023 / U:11.644 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site