From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/1] futex.2: simplify example
Date: Tue, 03 Mar 2015 09:05:51 +0100 [thread overview]
Message-ID: <54F56B5F.1070408@gmail.com> (raw)
In-Reply-To: <1425086747-4548-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
On 02/28/2015 02:25 AM, Heinrich Schuchardt wrote:
> Do not duplicate coding.
Thanks, Heinrich. Applied.
Cheers,
Michael
> Signed-off-by: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
> ---
> man2/futex.2 | 19 +++++--------------
> 1 file changed, 5 insertions(+), 14 deletions(-)
>
> diff --git a/man2/futex.2 b/man2/futex.2
> index 6c02da7..2d56a20 100644
> --- a/man2/futex.2
> +++ b/man2/futex.2
> @@ -1509,24 +1509,15 @@ fwait(int *futexp)
> machine\-language instructions. For further information, see
> the GCC Manual. */
>
> - /* Maybe the futex is already available: */
> -
> - if (__sync_bool_compare_and_swap(futexp, 1, 0))
> - return;
> -
> - /* No; we must wait for the futex value to be changed */
> -
> while (1) {
> - s = futex(futexp, FUTEX_WAIT, 0, NULL, NULL, 0);
> - if (s == \-1 && errno != EAGAIN)
> - errExit("futex\-FUTEX_WAIT");
> -
> - /* Is the futex now available? */
> -
> + /* Is the futex available? */
> if (__sync_bool_compare_and_swap(futexp, 1, 0))
> break; /* Yes */
>
> - /* Futex is still not available; wait again */
> + /* Futex is not available; wait */
> + s = futex(futexp, FUTEX_WAIT, 0, NULL, NULL, 0);
> + if (s == \-1 && errno != EAGAIN)
> + errExit("futex\-FUTEX_WAIT");
> }
> }
>
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-03-03 8:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 1:25 [PATCH 1/1] futex.2: simplify example Heinrich Schuchardt
[not found] ` <1425086747-4548-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2015-03-03 8:05 ` Michael Kerrisk (man-pages) [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=54F56B5F.1070408@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=xypron.glpk-Mmb7MZpHnFY@public.gmane.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 NNTP newsgroup(s).