From: Duncan Sands <duncan.sands@deepbluecap.com>
To: paulmck@linux.vnet.ibm.com, Ingo Molnar <mingo@kernel.org>
Cc: Michael Sullivan <sully@msully.net>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
lttng-dev@lists.lttng.org, Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [lttng-dev] Alternative to signals/sys_membarrier() in liburcu
Date: Mon, 23 Mar 2015 10:35:10 +0100 [thread overview]
Message-ID: <550FDE4E.30201@free.fr> (raw)
In-Reply-To: <20150313141853.GE5412@linux.vnet.ibm.com>
> So, given the fact that the userspace RCU library does now see
> some real-world use, is it now time for Mathieu to resubmit his
> sys_membarrier() patch?
I'm using userspace RCU with success in financial software, so the LTTng project
isn't the only user. It works well, but it's not as fast as I'd like. My
profiling shows that the performance hit is coming from the memory barriers. So
I would very much like to see sys_membarrier go in.
Best wishes, Duncan.
prev parent reply other threads:[~2015-03-23 9:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANW5cDmTCM9ZmhN7-2eWUEYvD+Y=sGt2i7mecdPTTLHMcT8fPg@mail.gmail.com>
[not found] ` <867044376.285926.1426172227750.JavaMail.zimbra@efficios.com>
[not found] ` <CANW5cDkiZoysNM3rqb4v6Tj996ocsaSh=OZoBLfp4h7ZGb4bxg@mail.gmail.com>
[not found] ` <666590480.287502.1426193588471.JavaMail.zimbra@efficios.com>
2015-03-12 20:56 ` Alternative to signals/sys_membarrier() in liburcu Mathieu Desnoyers
2015-03-12 21:12 ` Paul E. McKenney
2015-03-14 21:06 ` Benjamin Herrenschmidt
2015-03-12 23:59 ` One Thousand Gnomes
2015-03-13 0:43 ` Mathieu Desnoyers
2015-03-12 21:47 ` Linus Torvalds
2015-03-12 22:30 ` Mathieu Desnoyers
2015-03-13 8:07 ` Ingo Molnar
2015-03-13 14:18 ` Paul E. McKenney
2015-03-23 9:35 ` Duncan Sands [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=550FDE4E.30201@free.fr \
--to=duncan.sands@deepbluecap.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lttng-dev@lists.lttng.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sully@msully.net \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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