From: "Arnd Bergmann" <arnd@arndb.de>
To: "Parav Pandit" <parav@nvidia.com>,
bagasdotme@gmail.com, "Alan Stern" <stern@rowland.harvard.edu>,
parri.andrea@gmail.com, "Will Deacon" <will@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
boqun.feng@gmail.com, "Nicholas Piggin" <npiggin@gmail.com>,
dhowells@redhat.com, j.alglave@ucl.ac.uk, luc.maranget@inria.fr,
"Paul E. McKenney" <paulmck@kernel.org>,
"Akira Yokosawa" <akiyks@gmail.com>,
dlustig@nvidia.com, "Joel Fernandes" <joel@joelfernandes.org>,
"Jonathan Corbet" <corbet@lwn.net>,
linux-kernel@vger.kernel.org,
Linux-Arch <linux-arch@vger.kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v4] locking/memory-barriers.txt: Improve documentation for writel() example
Date: Mon, 17 Oct 2022 22:55:00 +0200 [thread overview]
Message-ID: <d5faaf6f-7de5-49b0-92d6-9989ffbdbf2e@app.fastmail.com> (raw)
In-Reply-To: <20221010101331.29942-1-parav@nvidia.com>
On Mon, Oct 10, 2022, at 12:13 PM, Parav Pandit wrote:
> The cited commit describes that when using writel(), explcit wmb()
> is not needed. wmb() is an expensive barrier. writel() uses the needed
> platform specific barrier instead of expensive wmb().
>
> Hence update the example to be more accurate that matches the current
> implementation.
>
> commit 5846581e3563 ("locking/memory-barriers.txt: Fix broken DMA vs.
> MMIO ordering example")
>
> Signed-off-by: Parav Pandit <parav@nvidia.com>
I have no objections, though I still don't see a real need to change
the wording here.
Acked-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2022-10-17 20:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 10:13 [PATCH v4] locking/memory-barriers.txt: Improve documentation for writel() example Parav Pandit
2022-10-17 20:55 ` Arnd Bergmann [this message]
2022-10-18 1:37 ` Akira Yokosawa
2022-10-18 6:44 ` Arnd Bergmann
2022-10-18 7:40 ` Akira Yokosawa
2022-10-18 7:49 ` Arnd Bergmann
2022-10-18 9:23 ` Akira Yokosawa
2022-10-18 10:05 ` Will Deacon
2022-10-18 17:49 ` Paul E. McKenney
2022-10-18 20:33 ` Parav Pandit
2022-10-27 18:15 ` Paul E. McKenney
2022-10-27 18:24 ` Parav Pandit
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=d5faaf6f-7de5-49b0-92d6-9989ffbdbf2e@app.fastmail.com \
--to=arnd@arndb.de \
--cc=akiyks@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=j.alglave@ucl.ac.uk \
--cc=joel@joelfernandes.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=npiggin@gmail.com \
--cc=parav@nvidia.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will@kernel.org \
/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