From: Florian Weimer <fweimer@redhat.com>
To: "André Almeida" <andrealmeid@collabora.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
"Pierre-Loup A. Griffais" <pgriffais@valvesoftware.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, kernel@collabora.com,
krisman@collabora.com, shuah@kernel.org,
linux-kselftest@vger.kernel.org, rostedt@goodmis.org,
ryao@gentoo.org, dvhart@infradead.org, mingo@redhat.com,
z.figura12@gmail.com, steven@valvesoftware.com,
steven@liquorix.net, malteskarupke@web.de, carlos@redhat.com,
adhemerval.zanella@linaro.org, libc-alpha@sourceware.org,
linux-api@vger.kernel.org
Subject: Re: 'simple' futex interface [Was: [PATCH v3 1/4] futex: Implement mechanism to wait on any of several futexes]
Date: Thu, 05 Mar 2020 17:25:23 +0100 [thread overview]
Message-ID: <87imji7or0.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <52406c54-60b3-dcfe-65d8-4c425459e37b@collabora.com> ("André Almeida"'s message of "Thu, 5 Mar 2020 13:14:17 -0300")
* André Almeida:
> Thanks everyone for the feedback around our mechanism. Are the
> performance benefits of implementing a syscall to wait on a single futex
> significant enough to maintain it instead of just using
> `sys_futex_waitv()` with `nr_waiters = 1`? If we join both cases in a
> single interface, we may even add a new member for NUMA hint in `struct
> futex_wait`.
Some seccomp user might want to verify the address, and that's easier if
it's in an argument. But that's just a rather minor aspect.
Do you propose to drop the storage requirement for the NUMA hint
next to the futex completely?
Thanks,
Florian
next prev parent reply other threads:[~2020-03-05 16:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 21:45 [PATCH v3 0/4] Implement FUTEX_WAIT_MULTIPLE operation André Almeida
2020-02-13 21:45 ` [PATCH v3 1/4] futex: Implement mechanism to wait on any of several futexes André Almeida
2020-02-28 19:07 ` Peter Zijlstra
2020-02-28 19:49 ` Peter Zijlstra
2020-02-28 21:25 ` Thomas Gleixner
2020-02-29 0:29 ` Pierre-Loup A. Griffais
2020-02-29 10:27 ` Thomas Gleixner
2020-03-03 2:47 ` Pierre-Loup A. Griffais
2020-03-03 12:00 ` 'simple' futex interface [Was: [PATCH v3 1/4] futex: Implement mechanism to wait on any of several futexes] Peter Zijlstra
2020-03-03 13:00 ` Florian Weimer
2020-03-03 13:21 ` Peter Zijlstra
2020-03-03 13:47 ` Florian Weimer
2020-03-03 15:01 ` Peter Zijlstra
2020-03-05 16:14 ` André Almeida
2020-03-05 16:25 ` Florian Weimer [this message]
2020-03-05 18:51 ` Peter Zijlstra
2020-03-06 16:57 ` David Laight
2020-02-13 21:45 ` [PATCH v3 2/4] selftests: futex: Add FUTEX_WAIT_MULTIPLE timeout test André Almeida
2020-02-13 21:45 ` [PATCH v3 3/4] selftests: futex: Add FUTEX_WAIT_MULTIPLE wouldblock test André Almeida
2020-02-13 21:45 ` [PATCH v3 4/4] selftests: futex: Add FUTEX_WAIT_MULTIPLE wake up test André Almeida
2020-02-19 16:27 ` [PATCH v3 0/4] Implement FUTEX_WAIT_MULTIPLE operation shuah
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=87imji7or0.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=andrealmeid@collabora.com \
--cc=carlos@redhat.com \
--cc=dvhart@infradead.org \
--cc=kernel@collabora.com \
--cc=krisman@collabora.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=malteskarupke@web.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pgriffais@valvesoftware.com \
--cc=rostedt@goodmis.org \
--cc=ryao@gentoo.org \
--cc=shuah@kernel.org \
--cc=steven@liquorix.net \
--cc=steven@valvesoftware.com \
--cc=tglx@linutronix.de \
--cc=z.figura12@gmail.com \
/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.