From: jthumshirn@suse.de (Johannes Thumshirn)
Subject: [PATCH-4.5-v3 1/5] NVMe: Add controller removing state
Date: Thu, 18 Feb 2016 10:37:09 +0100 [thread overview]
Message-ID: <20160218093709.GR18134@c203.arch.suse.de> (raw)
In-Reply-To: <1455734215-20396-2-git-send-email-keith.busch@intel.com>
On Wed, Feb 17, 2016@11:36:51AM -0700, Keith Busch wrote:
> The patch is preparing for reducing the scope of the namespace mutex. It
> adds a removing state the namespace scan work uses to know if it is safe
> to proceed. The scan work is flushed after setting the device state so
> the removal path can safely walk the namespace list without locking it.
>
> Signed-off-by: Keith Busch <keith.busch at intel.com>
Reviewed-by: Johannes Thumshirn <jthumshirn at suse.de>
--
Johannes Thumshirn Storage
jthumshirn at suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2016-02-18 9:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 18:36 [PATCH-4.5-v3 0/5] NVMe hot plug stuff Keith Busch
2016-02-17 18:36 ` [PATCH-4.5-v3 1/5] NVMe: Add controller removing state Keith Busch
2016-02-18 4:09 ` Christoph Hellwig
2016-02-18 9:37 ` Johannes Thumshirn [this message]
2016-02-17 18:36 ` [PATCH-4.5-v3 2/5] NVMe: Fix namespace removal deadlock Keith Busch
2016-02-18 2:00 ` Wenbo Wang
2016-02-18 4:09 ` Christoph Hellwig
2016-02-18 16:26 ` Keith Busch
2016-02-18 9:39 ` Johannes Thumshirn
2016-02-21 16:17 ` Christoph Hellwig
2016-02-17 18:36 ` [PATCH-4.5-v3 3/5] NVMe: Simplify device reset failure Keith Busch
2016-02-17 18:36 ` [PATCH-4.5-v3 4/5] NVMe: Move error handling to failed reset handler Keith Busch
2016-02-18 4:11 ` Christoph Hellwig
2016-02-18 19:38 ` Keith Busch
2016-02-18 9:42 ` Johannes Thumshirn
2016-02-17 18:36 ` [PATCH-4.5-v3 5/5] NVMe: Don't unmap controller registers on reset Keith Busch
2016-02-18 9:45 ` Johannes Thumshirn
2016-02-21 16:15 ` 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=20160218093709.GR18134@c203.arch.suse.de \
--to=jthumshirn@suse.de \
/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).