From: "Zack Weinberg" <zack@owlfolio.org>
To: libc-alpha@sourceware.org
Cc: "Peter Zijlstra" <peterz@infradead.org>
Subject: Re: [PATCH v2 16/22] futex: Implement sys_futex_waitv()
Date: Wed, 06 Oct 2021 09:48:43 -0400 [thread overview]
Message-ID: <47b13460-27a4-474c-879b-ed1c668e5923@www.fastmail.com> (raw)
In-Reply-To: <20211006115022.GH174703@worktop.programming.kicks-ass.net>
On Wed, Oct 6, 2021, at 7:50 AM, Peter Zijlstra wrote:
> On Thu, Sep 23, 2021 at 02:11:05PM -0300, André Almeida wrote:
>> Returns the array index of one of the awakened futexes. There’s no given
>> information of how many were awakened, or any particular attribute of it
>> (if it’s the first awakened, if it is of the smaller index...).
>
> As per some native speakers on IRC, awaken isn't the right word. I've
> changed it like the below.
"woken" and "awoken" are also not the right word (my brain flags both as spelling errors). Suggestions below:
> - * Returns the array index of one of the awaken futexes. There's no given
> - * information of how many were awakened, or any particular attribute of it (if
> - * it's the first awakened, if it is of the smaller index...).
> + * Returns the array index of one of the woken futexes. There's no given
> + * information of how many were woken, or any particular attribute of it (if
> + * it's the first woken, if it is of the smaller index...).
"awakened" was the correct word in all three places here. The sentences are awkward, I might suggest
# Returns the array index of one of the awakened futexes.
# No further information is provided: any number of other
# futexes may also have been awakened by the same event, and
# if more than one futex was awakened, the returned index may
# refer to any one of them. (It is not necessarily the futex
# with the smallest index, nor the one most recently awakened,
# nor ...)
> - * @awaken: Index of the last awoken futex, if any. Used to notify the
> + * @woken: Index of the last woken futex, if any. Used to notify the
> * caller that it can return this index to userspace (return parameter)
'awakened' in both places here; also suggest changing 'last' to 'most recently'
> - * - 1 - One of the futexes was awaken by another thread
> + * - 1 - One of the futexes was woken by another thread
'awakened' again (you *could* say 'was woke' here but it sounds slangy).
> -static int futex_wait_multiple_setup(struct futex_vector *vs, int count, int *awaken)
> +static int futex_wait_multiple_setup(struct futex_vector *vs, int count, int *woken)
and again
> - * absorb any awake events, which cannot be done before the
> + * loose any wake events, which cannot be done before the
'wake events' is correct here, but you introduced an unrelated error: 'loose' is the opposite of 'tight', you want 'lose' with only one O.
> - * was awaken, we don't return error and return this index to
> + * was woken, we don't return error and return this index to
> * userspace
> */
> - *awaken = unqueue_multiple(vs, i);
> - if (*awaken >= 0)
> + *woken = unqueue_multiple(vs, i);
> + if (*woken >= 0)
'awakened' in all locations
> - * been awaken.
> + * been woken.
same here
> - /* A futex was awaken during setup */
> + /* A futex was woken during setup */
and here
zw
next prev parent reply other threads:[~2021-10-06 13:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 17:10 [PATCH v2 00/22] futex: splitup and waitv syscall André Almeida
2021-09-23 17:10 ` [PATCH v2 01/22] futex: Move to kernel/futex/ André Almeida
2021-09-23 17:10 ` [PATCH v2 02/22] futex: Split out syscalls André Almeida
2021-09-23 17:10 ` [PATCH v2 03/22] futex: Rename {,__}{,un}queue_me() André Almeida
2021-09-23 17:10 ` [PATCH v2 04/22] futex: Rename futex_wait_queue_me() André Almeida
2021-09-23 17:10 ` [PATCH v2 05/22] futex: Rename: queue_{,un}lock() André Almeida
2021-09-23 17:10 ` [PATCH v2 06/22] futex: Rename __unqueue_futex() André Almeida
2021-09-23 17:10 ` [PATCH v2 07/22] futex: Rename hash_futex() André Almeida
2021-09-23 17:10 ` [PATCH v2 08/22] futex: Rename: {get,cmpxchg}_futex_value_locked() André Almeida
2021-09-23 17:10 ` [PATCH v2 09/22] futex: Split out PI futex André Almeida
2021-09-23 17:10 ` [PATCH v2 10/22] futex: Rename: hb_waiter_{inc,dec,pending}() André Almeida
2021-09-23 17:11 ` [PATCH v2 11/22] futex: Rename: match_futex() André Almeida
2021-09-23 17:11 ` [PATCH v2 12/22] futex: Rename mark_wake_futex() André Almeida
2021-09-23 17:11 ` [PATCH v2 13/22] futex: Split out requeue André Almeida
2021-09-23 17:11 ` [PATCH v2 14/22] futex: Split out wait/wake André Almeida
2021-09-23 17:11 ` [PATCH v2 15/22] futex: Simplify double_lock_hb() André Almeida
2021-09-23 17:11 ` [PATCH v2 16/22] futex: Implement sys_futex_waitv() André Almeida
2021-10-06 11:50 ` Peter Zijlstra
2021-10-06 13:48 ` Zack Weinberg [this message]
2021-10-07 9:08 ` Peter Zijlstra
2021-10-07 13:27 ` Steven Rostedt
2021-09-23 17:11 ` [PATCH v2 17/22] futex,x86: Wire up sys_futex_waitv() André Almeida
2021-09-23 17:11 ` [PATCH v2 18/22] futex,arm: " André Almeida
2021-09-23 17:11 ` [PATCH v2 19/22] selftests: futex: Add sys_futex_waitv() test André Almeida
2021-09-23 17:11 ` [PATCH v2 20/22] selftests: futex: Test sys_futex_waitv() timeout André Almeida
2021-11-09 11:18 ` Vasily Gorbik
2021-11-09 12:52 ` André Almeida
2021-11-09 13:00 ` Adhemerval Zanella
2021-11-09 13:05 ` Arnd Bergmann
2021-09-23 17:11 ` [PATCH v2 21/22] selftests: futex: Test sys_futex_waitv() wouldblock André Almeida
2021-09-23 17:11 ` [PATCH v2 22/22] futex2: Documentation: Document sys_futex_waitv() uAPI André Almeida
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=47b13460-27a4-474c-879b-ed1c668e5923@www.fastmail.com \
--to=zack@owlfolio.org \
--cc=libc-alpha@sourceware.org \
--cc=peterz@infradead.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).