nvmf: set CAP.CQR as required by the spec
CAP.CQR indicates whether contiguous queues are required; this is meaningless in NVMe over Fabrics, since queue creation is handled implicitly for each connection, but the spec requires it to be set to 1. Change-Id: I6b05954eefa6928beecd7a640bbbdbd835c6b69a Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
This commit is contained in:
parent
27c38d2c0c
commit
594c19bf69
@ -126,7 +126,7 @@ nvmf_init_nvme_session_properties(struct nvmf_session *session)
|
||||
*(uint32_t *)&session->vcdata.sgls);
|
||||
|
||||
session->vcprop.cap.raw = 0;
|
||||
session->vcprop.cap.bits.cqr = 0; /* queues not contiguous */
|
||||
session->vcprop.cap.bits.cqr = 1;
|
||||
session->vcprop.cap.bits.mqes = (session->vcdata.maxcmd - 1); /* max queue depth */
|
||||
session->vcprop.cap.bits.ams = 0; /* optional arb mechanisms */
|
||||
session->vcprop.cap.bits.to = 1; /* ready timeout - 500 msec units */
|
||||
|
Loading…
x
Reference in New Issue
Block a user