From: David Ahern <dsahern@gmail.com>
To: Davidlohr Bueso <dave@stgolabs.net>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>, Mel Gorman <mgorman@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf-bench/futex: Fix hung wakeup tasks after requeueing
Date: Fri, 24 Apr 2015 11:50:36 -0600 [thread overview]
Message-ID: <553A826C.8070504@gmail.com> (raw)
In-Reply-To: <1429894848.10273.44.camel@stgolabs.net>
On 4/24/15 11:00 AM, Davidlohr Bueso wrote:
> This bug, while perhaps suggesting missing wakeups in kernel futex
> code, is merely a consequence of the crappy FUTEX_CMP_REQUEUE man
> page, incorrectly mentioning that the number of requeued tasks is
> in fact returned, not the wakeups. This patch acknowledges this
> and updates the corresponding futex_wake code around it.
Did you submit an update to fix the crappy man page?
next prev parent reply other threads:[~2015-04-24 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 17:00 [PATCH] perf-bench/futex: Fix hung wakeup tasks after requeueing Davidlohr Bueso
2015-04-24 17:50 ` David Ahern [this message]
2015-04-24 17:57 ` Davidlohr Bueso
2015-05-01 10:15 ` [tip:perf/urgent] perf bench futex: " tip-bot for Davidlohr Bueso
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=553A826C.8070504@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@kernel.org \
--cc=dave@stgolabs.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.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.