From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 6/6] nvme: track shared namespaces in a siblings list
Date: Mon, 19 Jun 2017 12:19:53 +0200 [thread overview]
Message-ID: <20170619101953.GA18746@lst.de> (raw)
In-Reply-To: <b42db191-1298-c879-a1de-1e39724edc9c@grimberg.me>
On Mon, Jun 19, 2017@01:12:54PM +0300, Sagi Grimberg wrote:
> General question, Would it make sense to invoke this search from the
> block layer as part of adding a new disk (a new block_device operation)?
> And should the sibling association maybe move up to struct block_device?
> (we could cache nvme_id_ns in nvme_ns for that to happen)?
For the block/nvme multipath code I need to expose the relationship
to the block layer. But the locking is already complicated enough as
is, so I want to keep the NVMe list as well with that.
next prev parent reply other threads:[~2017-06-19 10:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 9:57 track subsystem relationships and shared namespaces V2 Christoph Hellwig
2017-06-19 9:57 ` [PATCH 1/6] nvme: remove a misleading comment on strut nvme_ns Christoph Hellwig
2017-06-19 16:49 ` Keith Busch
2017-06-19 9:57 ` [PATCH 2/6] nvme: read the subsystem NQN from Identify Controller Christoph Hellwig
2017-06-19 11:44 ` Johannes Thumshirn
2017-06-19 16:50 ` Keith Busch
2017-06-19 9:57 ` [PATCH 3/6] nvme: simplify nvme_dev_attrs_are_visible Christoph Hellwig
2017-06-19 16:50 ` Keith Busch
2017-06-19 9:57 ` [PATCH 4/6] nvme-fabrics: verify that a controller returns the correct NQN Christoph Hellwig
2017-06-19 9:57 ` [PATCH 5/6] nvme: track subsystems Christoph Hellwig
2017-06-19 11:47 ` Johannes Thumshirn
2017-06-19 16:52 ` Keith Busch
2017-06-19 9:57 ` [PATCH 6/6] nvme: track shared namespaces in a siblings list Christoph Hellwig
2017-06-19 10:12 ` Sagi Grimberg
2017-06-19 10:19 ` Christoph Hellwig [this message]
2017-06-19 10:39 ` Sagi Grimberg
2017-06-19 10:42 ` Christoph Hellwig
2017-06-19 10:57 ` Sagi Grimberg
2017-06-19 10:59 ` Christoph Hellwig
2017-06-19 11:27 ` Sagi Grimberg
2017-06-19 13:00 ` Christoph Hellwig
2017-06-19 16:43 ` Sagi Grimberg
-- strict thread matches above, loose matches on Subject: below --
2017-06-15 16:34 track subsystem relationships and shared namespaces Christoph Hellwig
2017-06-15 16:35 ` [PATCH 6/6] nvme: track shared namespaces in a siblings list Christoph Hellwig
2017-06-15 16:49 ` Sagi Grimberg
2017-06-16 6:20 ` Christoph Hellwig
2017-06-18 8:17 ` Sagi Grimberg
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=20170619101953.GA18746@lst.de \
--to=hch@lst.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