From: Jon Derrick <jonathan.derrick@intel.com>
To: Parav Pandit <parav.pandit@avagotech.com>
Cc: linux-nvme@lists.infradead.org,
Matthew Wilcox <willy@linux.intel.com>,
Jens Axboe <axboe@kernel.dk>, Keith Busch <keith.busch@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] NVMe: Fixed race between nvme_thread & probe path.
Date: Fri, 26 Jun 2015 12:10:47 -0600 [thread overview]
Message-ID: <20150626181047.GA3128@localhost.localdomain> (raw)
In-Reply-To: <CAGgvQNRjgwRFdN54v7j5gnS1xEXpRADr=0WZO3iH4AcQaNsY8g@mail.gmail.com>
> >> + smp_wmb();
> >
> > This has been applied already as an explicit mb()
>
> Since these structure is only accessible by software, won't smp_wmb()
> sufficient enough?
>
Seems reasonable to me
WARNING: multiple messages have this Message-ID (diff)
From: jonathan.derrick@intel.com (Jon Derrick)
Subject: [PATCH] NVMe: Fixed race between nvme_thread & probe path.
Date: Fri, 26 Jun 2015 12:10:47 -0600 [thread overview]
Message-ID: <20150626181047.GA3128@localhost.localdomain> (raw)
In-Reply-To: <CAGgvQNRjgwRFdN54v7j5gnS1xEXpRADr=0WZO3iH4AcQaNsY8g@mail.gmail.com>
> >> + smp_wmb();
> >
> > This has been applied already as an explicit mb()
>
> Since these structure is only accessible by software, won't smp_wmb()
> sufficient enough?
>
Seems reasonable to me
next prev parent reply other threads:[~2015-06-26 18:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 10:43 [PATCH] NVMe: Fixed race between nvme_thread & probe path Parav Pandit
2015-06-18 10:43 ` Parav Pandit
2015-06-18 15:59 ` Jon Derrick
2015-06-18 15:59 ` Jon Derrick
2015-06-18 17:48 ` Parav Pandit
2015-06-18 17:48 ` Parav Pandit
2015-06-26 18:10 ` Jon Derrick [this message]
2015-06-26 18:10 ` 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=20150626181047.GA3128@localhost.localdomain \
--to=jonathan.derrick@intel.com \
--cc=axboe@kernel.dk \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=parav.pandit@avagotech.com \
--cc=willy@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.