From: Hannes Reinecke <hare@suse.com>
To: "Luis R. Rodriguez" <mcgrof@suse.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: jakub@redhat.com, parri.andrea@gmail.com,
ksummit-discuss@lists.linuxfoundation.org, peterz@infradead.org,
stern@rowland.harvard.edu, 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 08:09:29 +0200 [thread overview]
Message-ID: <f423b811-88a4-b8ca-6793-1a543e8dc88d@suse.com> (raw)
In-Reply-To: <20160725171416.GQ5537@wotan.suse.de>
On 07/25/2016 07:14 PM, Luis R. Rodriguez wrote:
> On Fri, Jul 22, 2016 at 09:44:11AM -0700, Paul E. McKenney wrote:
>> On Fri, Jul 22, 2016 at 11:34:35AM +0100, David Howells wrote:
>>> Earlier this year we had a discussion of the possibilities of using ISO C++11
>>> atomic operations inside the kernel to implement kernel atomic ops of sorts
>>> various, posted here:
>>>
>>> Subject: [RFC PATCH 00/15] Provide atomics and bitops implemented with ISO C++11 atomics
>>> Date: Wed, 18 May 2016 16:10:37 +0100
>>>
>>> Is it worth getting together to discuss these in person in one of the tech
>>> slots - especially if there are some gcc or llvm people available at plumbers
>>> who could join in?
>>>
>>>
>>> Further, Paul McKenney and others are assembling a memory model description.
>>
>> We are attempting to automate memory-barriers.txt, so that you could
>> provide fragments of C code, and the tool would tell you whether a given
>> outcome happens always, sometimes, or never. The current prototype
>> handles memory accesses, memory barriers, and RCU, but not yet locking
>> or read-modify-write atomics (though there is some vestigal support for
>> RMW atomics). We are currently playing whack-a-mole with odd corner cases
>> of various architectures' memory models. We are therefore also working
>> on ways of handling the resulting uncertainty. Good clean fun! ;-)
>
> Consider me interested in this discussion, patches, etc.
>
Same here.
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.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.com +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2016-07-26 6:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 10:34 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 [this message]
2016-07-26 13:10 ` Alan Stern
2016-07-26 13:35 ` Paul E. McKenney
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-28 10:41 ` Will Deacon
2016-08-02 13:42 ` Peter Zijlstra
2016-08-03 8:49 ` Will Deacon
2016-07-26 15:20 ` David Howells
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=f423b811-88a4-b8ca-6793-1a543e8dc88d@suse.com \
--to=hare@suse.com \
--cc=j.alglave@ucl.ac.uk \
--cc=jakub@redhat.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=luc.maranget@inria.fr \
--cc=mcgrof@suse.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox