From: Inaky Perez-Gonzalez <inaky@linux.intel.com>
To: linux-kernel@vger.kernel.org
Cc: joe.korty@ccur.com, robustmutexes@lists.osdl.org, george@mvista.com
Subject: [RFC] A more general timeout specification
Date: Wed, 18 May 2005 15:15:54 -0700 [thread overview]
Message-ID: <17035.48794.636650.724153@sodium.jf.intel.com> (raw)
In-Reply-To: <20050518201517.GA16193@tsunami.ccur.com>
>>>>> Joe Korty <joe.korty@ccur.com> writes:
> [ for comment only ] 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'.
> That is, all combinations of useful timeout attributes become
> possible.
...
The main reason why we are asking for this is that timeouts in POSIX
calls are always specified in an absolute form. Because most system
calls take it in a relative form, glibc has to call the kernel twice
(one to get the time, one to do the syscall with the computed delta).
By having new syscalls that take advantage of this timeout interface,
we can save this extra kernel call.
We believe it is generic enough for interfacing with user space
timeouts, although we'd like to hear feedback :)
--
Inaky
next prev parent reply other threads:[~2005-05-18 22:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 20:15 Joe Korty
2005-05-18 22:15 ` Inaky Perez-Gonzalez [this message]
2005-05-19 13:39 ` Joe Korty
2005-05-18 23:49 ` Andi Kleen
2005-05-19 13:24 ` Joe Korty
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
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=17035.48794.636650.724153@sodium.jf.intel.com \
--to=inaky@linux.intel.com \
--cc=george@mvista.com \
--cc=joe.korty@ccur.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
Powered by JetHome