From: Keith Busch <keith.busch@linux.intel.com>
To: Michal Wnukowski <wnukowski@google.com>
Cc: Jens Axboe <axboe@fb.com>, Sagi Grimberg <sagi@grimberg.me>,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
Keith Busch <keith.busch@intel.com>,
yigitfiliz@google.com, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] Bugfix for handling of shadow doorbell buffer.
Date: Tue, 14 Aug 2018 16:57:16 -0600 [thread overview]
Message-ID: <20180814225716.GA3224@localhost.localdomain> (raw)
In-Reply-To: <20180814221735.62804-1-wnukowski@google.com>
On Tue, Aug 14, 2018 at 03:17:35PM -0700, Michal Wnukowski wrote:
> /* Update dbbuf and return true if an MMIO is required */
> static bool nvme_dbbuf_update_and_check_event(u16 value, u32 *dbbuf_db,
> - volatile u32 *dbbuf_ei)
> + u32 *dbbuf_ei)
> {
> if (dbbuf_db) {
> u16 old_value;
> @@ -306,6 +306,12 @@ static bool nvme_dbbuf_update_and_check_event(u16 value, u32 *dbbuf_db,
> old_value = *dbbuf_db;
> *dbbuf_db = value;
>
> + /*
> + * Ensure that the doorbell is updated before reading
> + * the EventIdx from memory
> + */
> + mb();
> +
> if (!nvme_dbbuf_need_event(*dbbuf_ei, value, old_value))
> return false;
> }
You just want to ensure the '*dbbuf_db = value' isn't reordered, right?
The order dependency might be more obvious if done as:
WRITE_ONCE(*dbbuf_db, value);
if (!nvme_dbbuf_need_event(READ_ONCE(*dbbuf_ei), value, old_value))
return false;
And 'volatile' is again redundant.
next prev parent reply other threads:[~2018-08-14 22:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 22:17 [PATCH] Bugfix for handling of shadow doorbell buffer Michal Wnukowski
2018-08-14 22:57 ` Keith Busch [this message]
2018-08-14 23:16 ` Linus Torvalds
2018-08-14 23:49 ` Keith Busch
2018-08-15 1:35 ` Michal Wnukowski
2018-08-15 2:02 ` Linus Torvalds
2018-08-15 22:51 ` [PATCH v2] " Michal Wnukowski
2018-08-16 14:15 ` Keith Busch
2018-08-16 21:20 ` Sagi Grimberg
2018-08-17 7:07 ` Christoph Hellwig
2018-08-20 20:09 ` Michal Wnukowski
2018-08-17 7:10 ` [PATCH] " Christoph Hellwig
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=20180814225716.GA3224@localhost.localdomain \
--to=keith.busch@linux.intel.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=wnukowski@google.com \
--cc=yigitfiliz@google.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).