From b2ee0bc180fb4206101b690c228631f37c465e34 Mon Sep 17 00:00:00 2001 From: Jim Harris Date: Mon, 25 Apr 2022 17:43:11 +0000 Subject: [PATCH] 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 Change-Id: I6ad0606be07fd38bc6c2e3a8e4bb78225b3dfadc Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/12385 Community-CI: Broadcom CI Tested-by: SPDK CI Jenkins Reviewed-by: Changpeng Liu Reviewed-by: Shuhei Matsumoto --- lib/nvmf/ctrlr.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/nvmf/ctrlr.c b/lib/nvmf/ctrlr.c index 5e00af7a3..698ea6c00 100644 --- a/lib/nvmf/ctrlr.c +++ b/lib/nvmf/ctrlr.c @@ -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; }