From: David Howells <dhowells@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: jakub@redhat.com, peterz@infradead.org,
ksummit-discuss@lists.linuxfoundation.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:20:37 +0100 [thread overview]
Message-ID: <30817.1469546437@warthog.procyon.org.uk> (raw)
In-Reply-To: <1469545881.120686.335.camel@infradead.org>
David Woodhouse <dwmw2@infradead.org> wrote:
> 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.
I don't recall that. Possibly that was a track I wasn't in.
> 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".
Does the memory model for CPU/device interactions have to be the same as that
for CPU/CPU interactions? I guess with respect to locks, it does so that two
processors who both want to access a device don't trample over each other.
> Is that what Paul is working on, that you mention above?
Paul is working on a general overall description.
David
prev parent reply other threads:[~2016-07-26 15:20 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
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 [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=30817.1469546437@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--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