From: Joel Becker <jlbec@evilplan.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: frankeh@watson.ibm.com, matthew@hairy.beasts.org,
linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: Re: [PATCH] Re: futex and timeouts
Date: Fri, 15 Mar 2002 06:08:29 +0000 [thread overview]
Message-ID: <20020315060829.L4836@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20020314151846.EDCBF3FE07@smtp.linux.ibm.com> <E16lkRS-0001HN-00@wagner.rustcorp.com.au>
In-Reply-To: <E16lkRS-0001HN-00@wagner.rustcorp.com.au>; from rusty@rustcorp.com.au on Fri, Mar 15, 2002 at 04:39:50PM +1100
On Fri, Mar 15, 2002 at 04:39:50PM +1100, Rusty Russell wrote:
> Yep, sorry, my mistake. I suggest make it a relative "struct timespec
> *" (more futureproof that timeval). It would make sense to split the
> interface into futex_down and futex_up syuscalls, since futex_up
> doesn't need a timeout arg, but I haven't for the moment.
Why waste a syscall? The user is going to be using a library
wrapper. They don't have to know that futex_up() calls sys_futex(futex,
FUTEX_UP, NULL);
Joel
--
Life's Little Instruction Book #182
"Be romantic."
http://www.jlbec.org/
jlbec@evilplan.org
next prev parent reply other threads:[~2002-03-15 6:08 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
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 [this message]
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=20020315060829.L4836@parcelfarce.linux.theplanet.co.uk \
--to=jlbec@evilplan.org \
--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.