nvmf: make acwu 0-based based

ACWU is a 0's based value, and our intent is to
report that our target's ACWU is 1 block.  This means
we should report ACWU as 0, not 1.

Signed-off-by: Jim Harris <james.r.harris@intel.com>
Change-Id: I6ad0606be07fd38bc6c2e3a8e4bb78225b3dfadc
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/12385
Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Changpeng Liu <changpeng.liu@intel.com>
Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com>
This commit is contained in:
Jim Harris 2022-04-25 17:43:11 +00:00 committed by Tomasz Zawadzki
parent ab9c7a6a81
commit b2ee0bc180

View File

@ -2664,7 +2664,7 @@ spdk_nvmf_ctrlr_identify_ctrlr(struct spdk_nvmf_ctrlr *ctrlr, struct spdk_nvme_c
cdata->maxcmd = transport->opts.max_queue_depth;
cdata->sgls = ctrlr->cdata.sgls;
cdata->fuses.compare_and_write = 1;
cdata->acwu = 1;
cdata->acwu = 0; /* ACWU is 0-based. */
if (subsystem->flags.ana_reporting) {
cdata->mnan = subsystem->max_nsid;
}