From: "Christopher Friesen" <cfriesen@nortel.com>
To: joe.korty@ccur.com
Cc: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>,
akpm@osdl.org, george@mvista.com, johnstul@us.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: FW: [RFC] A more general timeout specification
Date: Wed, 31 Aug 2005 16:06:00 -0600 [thread overview]
Message-ID: <431629C8.8030201@nortel.com> (raw)
In-Reply-To: <20050831213430.GA11858@tsunami.ccur.com>
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
timeouts.
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"?
Chris
next prev parent reply other threads:[~2005-08-31 22:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 20:55 FW: [RFC] A more general timeout specification Perez-Gonzalez, Inaky
2005-08-31 21:15 ` Joe Korty
2005-08-31 21:20 ` Christopher Friesen
2005-08-31 21:34 ` Joe Korty
2005-08-31 22:06 ` Christopher Friesen [this message]
2005-08-31 22:10 ` Roman Zippel
-- strict thread matches above, loose matches on Subject: below --
2005-09-01 11:59 Perez-Gonzalez, Inaky
2005-09-01 12:55 ` Roman Zippel
2005-09-01 0:00 Perez-Gonzalez, Inaky
2005-09-01 9:19 ` Roman Zippel
2005-09-01 13:48 ` Joe Korty
2005-09-01 15:18 ` Roman Zippel
2005-08-31 23:24 Perez-Gonzalez, Inaky
2005-08-31 23:50 ` Roman Zippel
2005-09-01 0:08 ` Daniel Walker
2005-09-01 9:22 ` Roman Zippel
2005-09-01 13:53 ` Joe Korty
2005-09-01 13:50 ` Joe Korty
2005-09-01 14:32 ` Roman Zippel
2005-09-01 15:10 ` Daniel Walker
2005-09-01 15:11 ` Daniel Walker
2005-09-01 15:47 ` Joe Korty
2005-08-31 23:17 Perez-Gonzalez, Inaky
2005-08-31 22:15 Perez-Gonzalez, Inaky
2005-08-31 23:01 ` Roman Zippel
2005-08-31 22:11 Perez-Gonzalez, Inaky
2005-08-31 23:06 ` Christopher Friesen
2005-08-23 1:13 Perez-Gonzalez, Inaky
2005-05-18 20:15 Joe Korty
2005-07-29 1:52 ` FW: " Inaky Perez-Gonzalez
2005-08-22 22:56 ` john stultz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=431629C8.8030201@nortel.com \
--to=cfriesen@nortel.com \
--cc=akpm@osdl.org \
--cc=george@mvista.com \
--cc=inaky.perez-gonzalez@intel.com \
--cc=joe.korty@ccur.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.