Reduce NVME_MAX_IO_QUEUES to 1024.
Most devices today support far fewer than 1024, but this is a more reasonable default upper limit than the spec-defined 64K. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Ia8a6d80c3a5aa181f27c8354758c6ca468013d92
This commit is contained in:
parent
38ea764f6d
commit
366d931183
@ -39,7 +39,7 @@
|
||||
|
||||
struct nvme_driver g_nvme_driver = {
|
||||
.lock = NVME_MUTEX_INITIALIZER,
|
||||
.max_io_queues = NVME_MAX_IO_QUEUES
|
||||
.max_io_queues = DEFAULT_MAX_IO_QUEUES
|
||||
};
|
||||
|
||||
int32_t nvme_retry_count;
|
||||
|
@ -95,6 +95,13 @@
|
||||
/* Maximum log page size to fetch for AERs. */
|
||||
#define NVME_MAX_AER_LOG_SIZE (4096)
|
||||
|
||||
/*
|
||||
* NVME_MAX_IO_QUEUES in nvme_spec.h defines the 64K spec-limit, but this
|
||||
* define specifies the maximum number of queues this driver will actually
|
||||
* try to configure, if available.
|
||||
*/
|
||||
#define DEFAULT_MAX_IO_QUEUES (1024)
|
||||
|
||||
struct nvme_request {
|
||||
struct nvme_command cmd;
|
||||
|
||||
|
@ -37,7 +37,7 @@
|
||||
|
||||
struct nvme_driver g_nvme_driver = {
|
||||
.lock = NVME_MUTEX_INITIALIZER,
|
||||
.max_io_queues = NVME_MAX_IO_QUEUES
|
||||
.max_io_queues = DEFAULT_MAX_IO_QUEUES
|
||||
};
|
||||
|
||||
char outbuf[OUTBUF_SIZE];
|
||||
|
@ -37,7 +37,7 @@
|
||||
|
||||
struct nvme_driver g_nvme_driver = {
|
||||
.lock = NVME_MUTEX_INITIALIZER,
|
||||
.max_io_queues = NVME_MAX_IO_QUEUES,
|
||||
.max_io_queues = DEFAULT_MAX_IO_QUEUES,
|
||||
};
|
||||
|
||||
int32_t nvme_retry_count = 1;
|
||||
|
Loading…
Reference in New Issue
Block a user