Messages in this thread | | | From | Hubertus Franke <> | Subject | Re: [Lse-tech] Re: [PATCH] Re: futex and timeouts | Date | Mon, 18 Mar 2002 16:35:03 -0500 |
| |
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) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |