From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: jakub@redhat.com, parri.andrea@gmail.com,
ksummit-discuss@lists.linuxfoundation.org, peterz@infradead.org,
ramana.radhakrishnan@arm.com, luc.maranget@inria.fr,
j.alglave@ucl.ac.uk
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Memory model, using ISO C++11 atomic ops
Date: Tue, 26 Jul 2016 06:35:51 -0700 [thread overview]
Message-ID: <20160726133551.GU7094@linux.vnet.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1607260909420.12362-100000@netrider.rowland.org>
On Tue, Jul 26, 2016 at 09:10:32AM -0400, Alan Stern wrote:
> On Tue, 26 Jul 2016, Hannes Reinecke wrote:
>
> > I have been playing around with RCUs and memory barriers quite a lot
> > recently, and found some really 'odd' use-cases in the kernel which
> > would benefit from improvements here.
>
> Could you post one or two examples? It would be interesting to see
> what they involve.
I would be intersted as well!
Thanx, Paul
next prev parent reply other threads:[~2016-07-26 13:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 10:34 [Ksummit-discuss] [TECH TOPIC] Memory model, using ISO C++11 atomic ops David Howells
2016-07-22 16:44 ` Paul E. McKenney
2016-07-25 17:14 ` Luis R. Rodriguez
2016-07-26 6:09 ` Hannes Reinecke
2016-07-26 13:10 ` Alan Stern
2016-07-26 13:35 ` Paul E. McKenney [this message]
2016-07-29 1:06 ` Steven Rostedt
2016-07-26 15:23 ` Hannes Reinecke
2016-07-26 22:40 ` Paul E. McKenney
2016-07-23 20:21 ` Benjamin Herrenschmidt
2016-07-26 15:11 ` David Woodhouse
2016-07-26 15:20 ` David Howells
2016-07-28 10:41 ` Will Deacon
2016-08-02 13:42 ` Peter Zijlstra
2016-08-03 8:49 ` Will Deacon
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=20160726133551.GU7094@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=j.alglave@ucl.ac.uk \
--cc=jakub@redhat.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=luc.maranget@inria.fr \
--cc=parri.andrea@gmail.com \
--cc=peterz@infradead.org \
--cc=ramana.radhakrishnan@arm.com \
--cc=stern@rowland.harvard.edu \
/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.