[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ef66595c-95cd-94c4-7f51-d3d7683a188a@grimberg.me>
Date: Wed, 13 Sep 2023 13:51:15 +0300
From: Sagi Grimberg <sagi@...mberg.me>
To: Aurelien Aptel <aaptel@...dia.com>, linux-nvme@...ts.infradead.org,
netdev@...r.kernel.org, hch@....de, kbusch@...nel.org, axboe@...com,
chaitanyak@...dia.com, davem@...emloft.net, kuba@...nel.org
Cc: Boris Pismenny <borisp@...dia.com>, aurelien.aptel@...il.com,
smalin@...dia.com, malin1024@...il.com, ogerlitz@...dia.com,
yorayz@...dia.com, galshalom@...dia.com, mgurtovoy@...dia.com
Subject: Re: [PATCH v15 06/20] nvme-tcp: Add DDP data-path
> @@ -1235,6 +1330,9 @@ static int nvme_tcp_try_send_cmd_pdu(struct nvme_tcp_request *req)
> else
> msg.msg_flags |= MSG_EOR;
>
> + if (test_bit(NVME_TCP_Q_OFF_DDP, &queue->flags))
> + nvme_tcp_setup_ddp(queue, blk_mq_rq_from_pdu(req));
Didn't we agree that setup_ddp should move to setup time and
not send time?
Powered by blists - more mailing lists