diff options
| author | jimharris <jimharris@FreeBSD.org> | 2016-02-11 17:32:41 +0000 |
|---|---|---|
| committer | jimharris <jimharris@FreeBSD.org> | 2016-02-11 17:32:41 +0000 |
| commit | 4deaf20e8bec867d08b7d8888468b2f9e83632be (patch) | |
| tree | 8afb2f9d718de2bbaca405d78a1ab0ce3c06c89a /contrib/llvm/lib/CodeGen/MIRPrintingPass.cpp | |
| parent | 51b30e8967e6d3ca63e740b2ffa317c7179fbdee (diff) | |
| download | FreeBSD-src-4deaf20e8bec867d08b7d8888468b2f9e83632be.zip FreeBSD-src-4deaf20e8bec867d08b7d8888468b2f9e83632be.tar.gz | |
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
Diffstat (limited to 'contrib/llvm/lib/CodeGen/MIRPrintingPass.cpp')
0 files changed, 0 insertions, 0 deletions
