mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael Kerrisk \(man-pages\)" <mtk.manpages@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Darren Hart <dvhart@linux.intel.com>
Cc: mtk.manpages@gmail.com, "Carlos O'Donell" <carlos@redhat.com>,
	Darren Hart <dvhart@linux.intel.com>, Ingo Molnar <mingo@elte.hu>,
	Jakub Jelinek <jakub@redhat.com>,
	"linux-man\@vger.kernel.org" <linux-man@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Davidlohr Bueso <dave@stgolabs.net>,
	Arnd Bergmann <arnd@arndb.de>,
	Steven Rostedt <rostedt@goodmis.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Linux API <linux-api@vger.kernel.org>,
	Torvald Riegel <triegel@redhat.com>,
	Roland McGrath <roland@hack.frob.com>,
	Darren Hart <dvhart@infradead.org>,
	Anton Blanchard <anton@samba.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Eric Dumazet <edumazet@google.com>,
	bill o gallmeister <bgallmeister@gmail.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Daniel Wagner <wagi@monom.org>, Rich Felker <dalias@libc.org>,
	Andy Lutomirski <luto@amacapital.net>,
	bert hubert <bert.hubert@netherlabs.nl>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: Revised futex(2) man page for review
Date: Tue, 31 Mar 2015 12:18:41 +1030	[thread overview]
Message-ID: <871tk6os1y.fsf@rustcorp.com.au> (raw)
In-Reply-To: <55166C01.7000803@gmail.com>

"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com> writes:
> When executing a 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

Missing 'e' in "space".

> .\" FIXME Please confirm that the following is correct:
> No guarantee is provided about which waiters are awoken
> (e.g., a waiter with a higher scheduling priority is not guaranteed
> to be awoken in preference to a waiter with a lower priority).

This is true.

I didn't read the rest, as that stuff was all written by others.
Documenting them is pretty heroic; good job!

Thanks,
Rusty.

  parent reply	other threads:[~2015-03-31  3:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-28  8:53 Michael Kerrisk (man-pages)
2015-03-28  8:56 ` Michael Kerrisk (man-pages)
2015-03-28 11:47 ` Peter Zijlstra
2015-03-28 12:03   ` Peter Zijlstra
2015-03-31 20:36     ` Davidlohr Bueso
2015-07-27 11:00       ` Michael Kerrisk (man-pages)
2015-07-27 11:10     ` Michael Kerrisk (man-pages)
2015-03-31 14:45   ` Davidlohr Bueso
2015-07-27 11:10     ` Michael Kerrisk (man-pages)
2015-07-28  3:16       ` Davidlohr Bueso
2015-07-28  7:44         ` Michael Kerrisk (man-pages)
2015-07-28 17:52           ` Davidlohr Bueso
2015-07-28 18:09             ` Michael Kerrisk (man-pages)
2015-04-14 21:40   ` Thomas Gleixner
2015-04-15 10:28     ` Torvald Riegel
2015-07-27 11:10       ` Michael Kerrisk (man-pages)
2015-04-27 20:37   ` Pavel Machek
2015-07-27 11:10     ` Michael Kerrisk (man-pages)
2015-07-28  2:52   ` Davidlohr Bueso
2015-07-28  6:39     ` Michael Kerrisk (man-pages)
2015-03-31  1:48 ` Rusty Russell [this message]
2015-07-27 11:03   ` Michael Kerrisk (man-pages)

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=871tk6os1y.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=anton@samba.org \
    --cc=arnd@arndb.de \
    --cc=bert.hubert@netherlabs.nl \
    --cc=bgallmeister@gmail.com \
    --cc=carlos@redhat.com \
    --cc=dalias@libc.org \
    --cc=dave@stgolabs.net \
    --cc=dvhart@infradead.org \
    --cc=dvhart@linux.intel.com \
    --cc=edumazet@google.com \
    --cc=jakub@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@elte.hu \
    --cc=mtk.manpages@gmail.com \
    --cc=peterz@infradead.org \
    --cc=roland@hack.frob.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=triegel@redhat.com \
    --cc=wagi@monom.org \
    --cc=xypron.glpk@gmx.de \
    /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

Powered by JetHome