From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Dave Watson <davejwatson@fb.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, Boqun Feng <boqun.feng@gmail.com>,
Andrew Hunter <ahh@google.com>,
Maged Michael <maged.michael@gmail.com>,
gromer@google.com, Avi Kivity <avi@scylladb.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH v4] membarrier: expedited private command
Date: Mon, 31 Jul 2017 12:44:24 -0700 [thread overview]
Message-ID: <20170731194424.GO3730@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170731192344.GA79955@dhcp-172-20-173-153.dhcp.thefacebook.com>
On Mon, Jul 31, 2017 at 12:23:44PM -0700, Dave Watson wrote:
> On 07/28/17 04:40 PM, Mathieu Desnoyers wrote:
> > Implement MEMBARRIER_CMD_PRIVATE_EXPEDITED with IPIs using cpumask built
> > from all runqueues for which current thread's mm is the same as the
> > thread calling sys_membarrier. It executes faster than the non-expedited
> > variant (no blocking). It also works on NOHZ_FULL configurations.
>
> I tested this with our hazard pointer use case on x86_64, and it seems
> to work great. We don't currently have any uses needing SHARED.
>
> Tested-by: Dave Watson <davejwatson@fb.com>
Applied, and thank you for testing this!
Thanx, Paul
prev parent reply other threads:[~2017-07-31 19:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 20:40 [PATCH v4] membarrier: expedited private command Mathieu Desnoyers
2017-07-28 20:58 ` Paul E. McKenney
2017-07-31 19:23 ` Dave Watson
2017-07-31 19:44 ` Paul E. McKenney [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=20170731194424.GO3730@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=ahh@google.com \
--cc=avi@scylladb.com \
--cc=benh@kernel.crashing.org \
--cc=boqun.feng@gmail.com \
--cc=davejwatson@fb.com \
--cc=gromer@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maged.michael@gmail.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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 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.