Re: [RFC 0/2] nvme/loop: Add support for controllers-per-port model

On Thu, 2016-06-09 at 15:39 +0200, Christoph Hellwig wrote: > On Wed, Jun 08, 2016 at 10:13:53PM -0700, Nicholas A. Bellinger wrote: > > I still don't see why a loopback controller on a port of an individual > > subsystem NQN can't be created + deleted directly from configfs, and > > operate

Re: [RFC 0/2] nvme/loop: Add support for controllers-per-port model

On Wed, Jun 08, 2016 at 10:13:53PM -0700, Nicholas A. Bellinger wrote: > I still don't see why a loopback controller on a port of an individual > subsystem NQN can't be created + deleted directly from configfs, and > operate independently of other loopback controllers on a port of a > different

Re: [RFC 0/2] nvme/loop: Add support for controllers-per-port model

On Wed, 2016-06-08 at 14:14 +0200, Christoph Hellwig wrote: > Hi Nic, > > multiple ports have been on the todo list ever since we put that short > cut in place, but your patches aren't really how this should work. > > The host NQN is not available for the actual drivers - we need to be able > to

Re: [RFC 0/2] nvme/loop: Add support for controllers-per-port model

Hi Nic, multiple ports have been on the todo list ever since we put that short cut in place, but your patches aren't really how this should work. The host NQN is not available for the actual drivers - we need to be able to virtualize it for containers for example, that's why we need to pass it

[RFC 0/2] nvme/loop: Add support for controllers-per-port model

From: Nicholas Bellinger Hi again folks, So building on the nvmet/configfs-ng WIP posted yesterday: http://marc.info/?l=linux-scsi=146528147018404=2 This series adds support for nvme/loop to utilize a nvme host controller per nvmet_port, instead of a single hardcoded