From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Laight <David.Laight@ACULAB.COM>
Cc: Scott Wood <scottwood@freescale.com>,
LinuxPPC-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: What is the reel purpose of in_beXX() and out_beXX() fonctions ?
Date: Tue, 28 Oct 2014 08:11:26 +1100 [thread overview]
Message-ID: <1414444286.364.193.camel@pasglop> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D1C9DFACE@AcuExch.aculab.com>
On Mon, 2014-10-27 at 15:05 +0000, David Laight wrote:
>
> Unfortunately the functions sometimes contain additional (often
> unneeded)
> sequencing instructions - the driver may be able to perform multiple
> operations between the sequencing instructions.
That's in part why some folks are working on proper relaxed accessors
(see Will Deacon's stuff)
Cheers,
Ben.
next prev parent reply other threads:[~2014-10-27 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 12:52 What is the reel purpose of in_beXX() and out_beXX() fonctions ? leroy christophe
2014-10-27 15:05 ` David Laight
2014-10-27 21:11 ` Benjamin Herrenschmidt [this message]
2014-10-27 16:45 ` Scott Wood
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=1414444286.364.193.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=David.Laight@ACULAB.COM \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.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;
as well as URLs for NNTP newsgroup(s).