]> CyberLeo.Net >> Repos - FreeBSD/stable/10.git/commit
MFC r295532:
authorjimharris <jimharris@ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f>
Wed, 17 Feb 2016 15:36:02 +0000 (15:36 +0000)
committerjimharris <jimharris@ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f>
Wed, 17 Feb 2016 15:36:02 +0000 (15:36 +0000)
commitd36dfc94cfb06088f84722d39137e33f065ee431
tree96ba492b3a9b43a649d80a16f4417f42e24c530a
parentd3ce66fa7a0495bcd7027989507807a32d4d13db
MFC r295532:

  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.

Approved by: re (glebius)
Sponsored by: Intel

git-svn-id: svn://svn.freebsd.org/base/stable/10@295704 ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
sys/dev/nvme/nvme_ctrlr.c