[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87a6s5w0us.fsf@collabora.com>
Date: Mon, 15 Feb 2021 15:08:11 -0500
From: Gabriel Krisman Bertazi <krisman@...labora.com>
To: André Almeida <andrealmeid@...labora.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Darren Hart <dvhart@...radead.org>,
linux-kernel@...r.kernel.org, Steven Rostedt <rostedt@...dmis.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
kernel@...labora.com, pgriffais@...vesoftware.com,
z.figura12@...il.com, joel@...lfernandes.org,
malteskarupke@...tmail.fm, linux-api@...r.kernel.org,
fweimer@...hat.com, libc-alpha@...rceware.org,
linux-kselftest@...r.kernel.org, shuah@...nel.org, acme@...nel.org,
corbet@....net
Subject: Re: [RFC PATCH 03/13] futex2: Implement vectorized wait
André Almeida <andrealmeid@...labora.com> writes:
> Add support to wait on multiple futexes. This is the interface
> implemented by this syscall:
>
> futex_waitv(struct futex_waitv *waiters, unsigned int nr_futexes,
> unsigned int flags, struct timespec *timo)
Sorry for the second email in a row. But, if futex_wake is just a
futex_wakev with nr_futexes == 1, why do we need two syscalls for that?
Why not only have futex_waitv?
--
Gabriel Krisman Bertazi
Powered by blists - more mailing lists