diff options
| author | jimharris <jimharris@FreeBSD.org> | 2016-02-17 15:36:02 +0000 |
|---|---|---|
| committer | jimharris <jimharris@FreeBSD.org> | 2016-02-17 15:36:02 +0000 |
| commit | b9d4be0c4e918d40c0526998dc097fccb3d08426 (patch) | |
| tree | 96ba492b3a9b43a649d80a16f4417f42e24c530a /lib/libc/stdlib/labs.c | |
| parent | 4aef3019513be35be30d1ea8ff5b072a743f99df (diff) | |
| download | FreeBSD-src-b9d4be0c4e918d40c0526998dc097fccb3d08426.zip FreeBSD-src-b9d4be0c4e918d40c0526998dc097fccb3d08426.tar.gz | |
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
Diffstat (limited to 'lib/libc/stdlib/labs.c')
0 files changed, 0 insertions, 0 deletions
