From: David Woodhouse <dwmw2@infradead.org>
To: David Howells <dhowells@redhat.com>,
ksummit-discuss@lists.linuxfoundation.org
Cc: jakub@redhat.com, peterz@infradead.org, ramana.radhakrishnan@arm.com
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Memory model, using ISO C++11 atomic ops
Date: Tue, 26 Jul 2016 16:11:21 +0100 [thread overview]
Message-ID: <1469545881.120686.335.camel@infradead.org> (raw)
In-Reply-To: <15500.1469183675@warthog.procyon.org.uk>
[-- Attachment #1: Type: text/plain, Size: 909 bytes --]
On Fri, 2016-07-22 at 11:34 +0100, David Howells wrote:
> Further, Paul McKenney and others are assembling a memory model description.
> Do we want to consider loosening up the kernel memory model?
It's not clear that 'loosening up' is what we're after.
In Seoul last year, weren't we looking at things like readl_relaxed()
and lamenting the fact that they do actually still have strong enough
requirements that they can't *really* be very relaxed on Power and
ARM64 at all, because they're basically being used with the assumption
of Intel-like semantics.
The cheap answer is "well, it sucks to be on POWER or ARM64 because
then readl_relaxed() has to be as slow as readl() is".
But it would be good to follow up on that properly, and maybe introduce
a variant which *can* be implemented across more architectures.
Is that what Paul is working on, that you mention above?
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5760 bytes --]
next prev parent reply other threads:[~2016-07-26 15:11 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
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 [this message]
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=1469545881.120686.335.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=dhowells@redhat.com \
--cc=jakub@redhat.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=peterz@infradead.org \
--cc=ramana.radhakrishnan@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox