[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d23e33e7-d545-2ad0-d163-5182dd5430b1@grimberg.me>
Date: Fri, 23 Oct 2020 11:01:40 -0700
From: Sagi Grimberg <sagi@...mberg.me>
To: zhenwei pi <pizhenwei@...edance.com>, kbusch@...nel.org,
hch@....de, axboe@...com
Cc: linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] nvme-rdma: handle nvme completion data length
> diff --git a/drivers/nvme/host/rdma.c b/drivers/nvme/host/rdma.c
> index 9e378d0a0c01..2ecadd309f4a 100644
> --- a/drivers/nvme/host/rdma.c
> +++ b/drivers/nvme/host/rdma.c
> @@ -1767,6 +1767,21 @@ static void nvme_rdma_recv_done(struct ib_cq *cq, struct ib_wc *wc)
> return;
> }
>
> + /* received data length checking */
> + if (unlikely(wc->byte_len < len)) {
> + /* zero bytes message could be ignored */
> + if (!wc->byte_len) {
> + nvme_rdma_post_recv(queue, qe);
> + return;
> + }
Nothing in the spec defines zero-length messages, hence we cannot
support something that is not standard. If your array needs this,
please submit a TPAR to the NVMe TWG.
Powered by blists - more mailing lists