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: explanation of blocking behavior
Date: Sat, 11 Apr 2015 08:59:58 +0200 [thread overview]
Message-ID: <5528C66E.8070900@gmail.com> (raw)
In-Reply-To: <1427654900-30075-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
On 03/29/2015 08:48 PM, Heinrich Schuchardt wrote:
> Shorten overlong sentence.
> Highlight futex().
> Tfix.
Thanks, Heinrich. Applied.
Cheers,
Michael
> Signed-off-by: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
> ---
> man2/futex.2 | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/man2/futex.2 b/man2/futex.2
> index 0644fc6..dea50ea 100644
> --- a/man2/futex.2
> +++ b/man2/futex.2
> @@ -59,16 +59,18 @@ in separate processes may be different,
> the same physical address may be shared by the processes using
> .BR mmap (2).)
>
> -When executing a futex operation that requests to block a thread,
> +When executing a
> +.BR futex ()
> +operation that requests to block a thread,
> the kernel will only block if the futex word has the value that the
> calling thread supplied as expected value.
> The load from the futex word, the comparison with
> the expected value,
> and the actual blocking will happen atomically and totally
> -ordered with respect to concurrently executing futex operations
> -on the same futex word,
> -such as operations that wake threads blocked on this futex word.
> -Thus, the futex word is used to connect the synchronization in user spac
> +ordered with respect to concurrently executing
> +.BR futex ()
> +operations on the same futex word.
> +Thus, the futex word is used to connect the synchronization in user space
> with the implementation of blocking by the kernel; similar to an atomic
> compare-and-exchange operation that potentially changes shared memory,
> blocking via a futex is an atomic compare-and-block operation.
>
--
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-04-11 6:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-29 18:48 [PATCH 1/1] futex.2: explanation of blocking behavior Heinrich Schuchardt
[not found] ` <1427654900-30075-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2015-04-11 6:59 ` 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=5528C66E.8070900@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 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.