From: Ulrich Drepper <drepper@redhat.com>
To: frankeh@watson.ibm.com
Cc: rusty@rustcorp.com.au, matthew@hairy.beasts.org,
linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: Re: futex and timeouts
Date: 13 Mar 2002 10:54:54 -0800 [thread overview]
Message-ID: <1016045694.16743.1046.camel@myware.mynet> (raw)
In-Reply-To: <20020313182552.945523FE06@smtp.linux.ibm.com>
In-Reply-To: <20020313182552.945523FE06@smtp.linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 750 bytes --]
On Wed, 2002-03-13 at 10:26, Hubertus Franke wrote:
> Ulrich, it seems to me that absolute timeouts are the easiest to do.
Does it work with settimeofday()?
> Question is whether the granularity of jiffies (10ms) is sufficiently small
> for timeouts.....
Hopefully there will be support for high-resolution clocks and timers
sometime soon. I don't know how to prepare new interfaces for this. I
guess there will be a whole bunch of interface changes/additions so you
could ignore the problem for now.
--
---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-03-13 18:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 18:26 futex and timeouts Hubertus Franke
2002-03-13 18:54 ` Ulrich Drepper [this message]
2002-03-14 4:15 ` Rusty Russell
2002-03-14 15:19 ` Hubertus Franke
2002-03-15 5:39 ` [PATCH] " Rusty Russell
2002-03-15 6:08 ` Joel Becker
2002-03-15 6:56 ` H. Peter Anvin
2002-03-15 8:49 ` Rusty Russell
2002-03-15 15:16 ` Hubertus Franke
2002-03-15 16:04 ` Joel Becker
2002-03-15 18:59 ` Hubertus Franke
2002-03-15 19:28 ` Joel Becker
2002-03-16 1:12 ` [Lse-tech] " george anzinger
2002-03-18 21:35 ` Hubertus Franke
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=1016045694.16743.1046.camel@myware.mynet \
--to=drepper@redhat.com \
--cc=frankeh@watson.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=matthew@hairy.beasts.org \
--cc=rusty@rustcorp.com.au \
/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.