[PATCH 6/6] nvme: track shared namespaces in a siblings list

[Christoph Hellwig]

On Mon, Jun 19, 2017 at 01:57:19PM +0300, Sagi Grimberg wrote:
> Didn't mean driver specific locking on the sibling list itself,
> just on the sibling search. The sibling list should obviously have its
> own locking. You have yet to reveal how the block layer should handle
> the siblings, but I imagine you have some family representation, which
> will have its own locking scheme to manage siblings/paths.

Oh.  No, I don't want to do the search in the block layer at all.

The are two (or more) request_queues siblings thing makes total sense
for the block layer.  But how we decide that fact is totally driver
specifіc.  E.g. for SCSI the search would look completely different
as we don't have the equivalent of the controllers per subsystem
list.