linux.git/drivers/nvme/target/loop.c, branch v4.13

nvme: split nvme_uninit_ctrl into stop and uninit

2017-07-06T06:49:42+00:00

Usually before we teardown the controller we want to:
1. complete/cancel any ctrl inflight works
2. remove ctrl namespaces (only for removal though, resets
   shouldn't remove any namespaces).

but we do not want to destroy the controller device as
we might use it for logging during the teardown stage.

This patch adds nvme_start_ctrl() which queues inflight
controller works (aen, ns scan, queue start and keep-alive
if kato is set) and nvme_stop_ctrl() which cancels the works
namespace removal is left to the callers to handle.

Move nvme_uninit_ctrl after we are done with the
controller device.

Reviewed-by: Keith Busch 
Reviewed-by: Christoph Hellwig 
Signed-off-by: Sagi Grimberg

nvme-loop: quiesce/unquiesce admin_q instead of start/stop its hw queues

2017-07-06T06:48:43+00:00

unlike blk_mq_stop_hw_queues and blk_mq_start_stopped_hw_queues
quiescing/unquiescing respects the submission path rcu grace.

Reviewed-by: Ming Lei 
Signed-off-by: Sagi Grimberg

nvme-loop: update tagset nr_hw_queues after reconnecting/resetting

2017-07-04T06:44:16+00:00

We might have more/less queues once we reconnect/reset. For
example due to cpu going online/offline

Reviewed-by: Johannes Thumshirn 
Reviewed-by: Christoph Hellwig 
Signed-off-by: Sagi Grimberg

nvme: move ctrl cap to struct nvme_ctrl

2017-07-02T12:03:22+00:00

All transports use either a private cache of controller cap or an on-stack
copy, move it to the generic struct nvme_ctrl. In the future it will also
be maintained by the core.

Reviewed-by: Christoph Hellwig 
Reviewed-by: Johannes Thumshirn 
Reviewed-by: Max Gurtovoy 
Signed-off-by: Sagi Grimberg

nvme: move queue_count to the nvme_ctrl

2017-07-02T11:59:04+00:00

All all transports use the queue_count in exactly the same, so move it to
the generic struct nvme_ctrl. In the future it will also be maintained by
the core.

Reviewed-by: Christoph Hellwig 
Reviewed-By: James Smart 
Reviewed-by: Johannes Thumshirn 
Reviewed-by: Max Gurtovoy 
Signed-off-by: Sagi Grimberg

nvme: read the subsystem NQN from Identify Controller

2017-06-28T14:14:13+00:00

NVMe 1.2.1 or later requires controllers to provide a subsystem NQN in the
Identify controller data structures.  Use this NQN for the subsysnqn
sysfs attribute by storing it in the nvme_ctrl structure after verifying
it.  For older controllers we generate a "fake" NQN per non-normative
text in the NVMe 1.3 spec.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Keith Busch 
Reviewed-by: Johannes Thumshirn 
Signed-off-by: Sagi Grimberg 
Signed-off-by: Jens Axboe

nvme: use a single NVME_AQ_DEPTH and relax it to 32

2017-06-28T14:14:13+00:00

No need to differentiate fabrics from pci/loop, also lower
it to 32 as we don't really need 256 inflight admin commands.

Signed-off-by: Sagi Grimberg 
Reviewed-by: Martin K. Petersen 
Reviewed-by: Christoph Hellwig 
Reviewed-by: Max Gurtovoy 
Signed-off-by: Keith Busch 
Signed-off-by: Jens Axboe

nvme: move reset workqueue handling to common code

2017-06-15T13:48:34+00:00

This moves the nvme_reset function from the PCIe driver to common code,
renaming it to nvme_reset_ctrl in the process.  Additionally a new
helper nvme_reset_ctrl_sync is added for the case where we want to
wait for the reset.  To facilitate that the reset_work work structure is
move to the common nvme_ctrl structure and the ->reset_ctrl method is
removed.  For now the drivers initialize the reset_work with their own
callback, but longer term we should move to callouts for specific
parts of the reset process and move even more code to the core.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Sagi Grimberg

nvme-loop: merge init_request methods

2017-06-15T12:30:33+00:00

Now that we get the tagset passed we can have a single implementation for
the I/O and admin queues.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Max Gurtovoy 
Reviewed-by: Sagi Grimberg 
Signed-off-by: Christoph Hellwig

nvme: Move transports to use nvme-core workqueue

2017-06-15T12:29:43+00:00

Instead of each transport using it's own workqueue, export
a single nvme-core workqueue and use that instead.

In the future, this will help us moving towards some unification
if controller setup/teardown flows.

Signed-off-by: Sagi Grimberg 
Signed-off-by: Christoph Hellwig