From: Joe Korty <joe.korty@ccur.com>
To: Andi Kleen <ak@muc.de>
Cc: robustmutexes@lists.osdl.org, george@mvista.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] A more general timeout specification
Date: Thu, 19 May 2005 09:24:57 -0400 [thread overview]
Message-ID: <20050519132457.GA9357@tsunami.ccur.com> (raw)
In-Reply-To: <m1hdh0yu14.fsf@muc.de>
On Thu, May 19, 2005 at 01:49:11AM +0200, Andi Kleen wrote:
> Joe Korty <joe.korty@ccur.com> writes:
>
> > The fusyn (robust mutexes) project proposes the creation
> > of a more general data structure, 'struct timeout', for the
> > specification of timeouts in new services. In this structure,
> > the user specifies:
> >
> > a time, in timespec format.
> > the clock the time is specified against (eg, CLOCK_MONOTONIC).
> > whether the time is absolute, or relative to 'now'.
>
> If you do a new structure for this I would suggest adding a
> "precision" field (or the same with a different name). Basically
> precision would tell the kernel that the wakeup can be in a time
> range, not necessarily on the exact time specified.
Very cool.
Joe
next prev parent reply other threads:[~2005-05-19 13:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 20:15 [RFC] A more general timeout specification Joe Korty
2005-05-18 22:15 ` Inaky Perez-Gonzalez
2005-05-19 13:39 ` Joe Korty
2005-05-18 23:49 ` Andi Kleen
2005-05-19 13:24 ` Joe Korty [this message]
2005-05-19 17:02 ` George Anzinger
2005-05-19 18:35 ` Inaky Perez-Gonzalez
2005-05-20 19:05 ` Andi Kleen
2005-05-21 1:12 ` George Anzinger
2005-07-29 1:52 ` FW: " Inaky Perez-Gonzalez
2005-08-22 22:56 ` john stultz
-- strict thread matches above, loose matches on Subject: below --
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-09-01 21:20 ` Kyle Moffett
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=20050519132457.GA9357@tsunami.ccur.com \
--to=joe.korty@ccur.com \
--cc=ak@muc.de \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robustmutexes@lists.osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox