Jim Harris 7b036d7790 nvme: avoid duplicate SET_NUM_QUEUES commands ... nvme(4) issues a SET_NUM_QUEUES command during device initialization to ensure enough I/O queues exists for each of the MSI-X vectors we have allocated. The SET_NUM_QUEUES command is then issued again during nvme_ctrlr_start(), to ensure that is properly set after any controller reset. At least one NVMe drive exists which fails this second SET_NUM_QUEUES command during device initialization. So change nvme_ctrlr_start() to only issue its SET_NUM_QUEUES command when it is coming out of a reset - avoiding the duplicate SET_NUM_QUEUES during device initialization. Reported by: gallatin MFC after: 3 days Sponsored by: Intel		2016-02-11 17:32:41 +00:00
..
nvme.c	nvme: do not revert o single I/O queue when per-CPU queues not possible	2016-01-07 16:18:32 +00:00
nvme.h	Implement power command to list all power modes, find out the power	2016-01-30 22:48:06 +00:00
nvme_ctrlr.c	nvme: avoid duplicate SET_NUM_QUEUES commands	2016-02-11 17:32:41 +00:00
nvme_ctrlr_cmd.c
nvme_ns.c	Limit stripesize reported from nvd(4) to 4K	2015-12-11 02:06:03 +00:00
nvme_ns_cmd.c
nvme_private.h	nvme: do not revert o single I/O queue when per-CPU queues not possible	2016-01-07 16:18:32 +00:00
nvme_qpair.c	nvme: do not pre-allocate MSI-X IRQ resources	2016-01-07 16:11:31 +00:00
nvme_sysctl.c	nvme: add hw.nvme.min_cpus_per_ioq tunable	2016-01-07 20:32:04 +00:00
nvme_test.c
nvme_util.c