From: Hubertus Franke <frankeh@watson.ibm.com>
To: george anzinger <george@mvista.com>, Joel Becker <jlbec@evilplan.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
matthew@hairy.beasts.org, linux-kernel@vger.kernel.org,
lse-tech@lists.sourceforge.net
Subject: Re: [Lse-tech] Re: [PATCH] Re: futex and timeouts
Date: Mon, 18 Mar 2002 16:35:03 -0500 [thread overview]
Message-ID: <20020318213411.6E2BA3FE07@smtp.linux.ibm.com> (raw)
In-Reply-To: <20020314151846.EDCBF3FE07@smtp.linux.ibm.com> <20020315192818.R4836@parcelfarce.linux.theplanet.co.uk> <3C929BF0.3CDC58AB@mvista.com>
On Friday 15 March 2002 08:12 pm, george anzinger wrote:
> Joel Becker wrote:
> > On Fri, Mar 15, 2002 at 01:59:38PM -0500, Hubertus Franke wrote:
> > > > > What I would like to see is an interface that lets me pass optional
> > > > > parameters to the syscall interface, so I can call with different
> > > > > number of parameters.
> > > >
> > > > Is this to lock multiple futexes "atomically"? If we are
> > > > looking for a fast path stack-wise, this seems extra work.
> > >
> > > No, take for example...
> > >
> > > syscall3(int,futex,int,op, struct futex*, futex, int opt_arg);
>
> I don't think there is anything "broken" in defining more than one
> syscall stub to the same system call, each with a different parameter
> count (or completely different arguments). The call code will need to
> be able to figure it out, but there is nothing in the way as far as
> doing it.
>
> -g
>
Ofcourse, no difficulties here, but no convenient way either, as the
__NR_futex is automatically used.
--
-- Hubertus Franke (frankeh@watson.ibm.com)
prev parent reply other threads:[~2002-03-18 21:34 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
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 [this message]
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=20020318213411.6E2BA3FE07@smtp.linux.ibm.com \
--to=frankeh@watson.ibm.com \
--cc=george@mvista.com \
--cc=jlbec@evilplan.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).