From: axboe@kernel.dk (Jens Axboe)
Subject: [PATCH] NVMe: Memory barrier before queue_count is incremented
Date: Fri, 05 Jun 2015 10:34:02 -0600 [thread overview]
Message-ID: <5571CF7A.2050100@kernel.dk> (raw)
In-Reply-To: <alpine.LNX.2.00.1505282232260.15930@localhost.lm.intel.com>
On 05/28/2015 04:32 PM, Keith Busch wrote:
> On Wed, 27 May 2015, Jon Derrick wrote:
>> Protects against reordering and/or preempting which would allow the
>> kthread to access the queue descriptor before it is set up
>
> Looks good to me.
>
> Acked-by: Keith Busch <keith.busch at intel.com>
Ditto, merged.
--
Jens Axboe
next prev parent reply other threads:[~2015-06-05 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 18:26 [PATCH] NVMe: Memory barrier before queue_count is incremented Jon Derrick
2015-05-28 22:32 ` Keith Busch
2015-06-05 16:34 ` Jens Axboe [this message]
2015-06-03 16:26 ` Jon Derrick
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=5571CF7A.2050100@kernel.dk \
--to=axboe@kernel.dk \
/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