From: Aurelien Aptel <aaptel@nvidia.com>
To: Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, netdev@vger.kernel.org,
hch@lst.de, kbusch@kernel.org, axboe@fb.com,
chaitanyak@nvidia.com, davem@davemloft.net, kuba@kernel.org
Cc: Yoray Zack <yorayz@nvidia.com>,
aurelien.aptel@gmail.com, smalin@nvidia.com, malin1024@gmail.com,
ogerlitz@nvidia.com, borisp@nvidia.com, galshalom@nvidia.com,
mgurtovoy@nvidia.com
Subject: Re: [PATCH v20 07/20] nvme-tcp: RX DDGST offload
Date: Wed, 29 Nov 2023 15:56:54 +0200 [thread overview]
Message-ID: <253jzq0irx5.fsf@nvidia.com> (raw)
In-Reply-To: <bc6ec871-de51-477a-b27f-4d516e5bc3e1@grimberg.me>
Sagi Grimberg <sagi@grimberg.me> writes:
>> +static void nvme_tcp_ddp_ddgst_recalc(struct ahash_request *hash,
>> + struct request *rq,
>> + __le32 *ddgst)
>> +{
>> + struct nvme_tcp_request *req;
>> +
>> + if (!rq)
>> + return;
>
> How is this even possible? And what happens down the road if this is
> indeed a null rq?
You are correct, this isn't possible. We can see the req is fetched
earlier in nvme_tcp_recv_pdu() so it must exist.
We will remove it.
>> +
>> + req = blk_mq_rq_to_pdu(rq);
>> + ahash_request_set_crypt(hash, req->ddp.sg_table.sgl, (u8 *)ddgst,
>> + req->data_len);
>> + crypto_ahash_digest(hash);
>> +}
>> +
>> static bool nvme_tcp_resync_request(struct sock *sk, u32 seq, u32 flags);
>> static void nvme_tcp_ddp_teardown_done(void *ddp_ctx);
>> static const struct ulp_ddp_ulp_ops nvme_tcp_ddp_ulp_ops = {
>> @@ -430,6 +459,8 @@ static void nvme_tcp_setup_ddp(struct nvme_tcp_queue *queue,
>> static int nvme_tcp_offload_socket(struct nvme_tcp_queue *queue)
>> {
>> struct ulp_ddp_config config = {.type = ULP_DDP_NVME};
>> + bool offload_ddgst_rx = ulp_ddp_is_cap_active(queue->ctrl->ddp_netdev,
>> + ULP_DDP_CAP_NVME_TCP_DDGST_RX);
>
> Not sure a local variable is needed here.
Ok we will remove it.
Thanks
next prev parent reply other threads:[~2023-11-29 13:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 13:48 [PATCH v20 00/20] nvme-tcp receive offloads Aurelien Aptel
2023-11-22 13:48 ` [PATCH v20 01/20] net: Introduce direct data placement tcp offload Aurelien Aptel
2023-11-22 13:48 ` [PATCH v20 02/20] netlink: add new family to manage ULP_DDP enablement and stats Aurelien Aptel
2023-11-23 16:21 ` Jiri Pirko
2023-11-27 13:17 ` Aurelien Aptel
2023-11-22 13:48 ` [PATCH v20 03/20] iov_iter: skip copy if src == dst for direct data placement Aurelien Aptel
2023-11-22 13:48 ` [PATCH v20 04/20] net/tls,core: export get_netdev_for_sock Aurelien Aptel
2023-11-22 13:48 ` [PATCH v20 05/20] nvme-tcp: Add DDP offload control path Aurelien Aptel
2023-11-28 10:31 ` Sagi Grimberg
2023-11-29 13:52 ` Aurelien Aptel
2023-12-11 17:29 ` Max Gurtovoy
2023-12-13 9:49 ` Sagi Grimberg
2023-11-22 13:48 ` [PATCH v20 06/20] nvme-tcp: Add DDP data-path Aurelien Aptel
2023-11-28 10:40 ` Sagi Grimberg
2023-11-29 13:55 ` Aurelien Aptel
2023-11-22 13:48 ` [PATCH v20 07/20] nvme-tcp: RX DDGST offload Aurelien Aptel
2023-11-28 10:42 ` Sagi Grimberg
2023-11-29 13:56 ` Aurelien Aptel [this message]
2023-11-22 13:48 ` [PATCH v20 08/20] nvme-tcp: Deal with netdevice DOWN events Aurelien Aptel
2023-11-28 10:44 ` Sagi Grimberg
2023-11-22 13:48 ` [PATCH v20 09/20] Documentation: add ULP DDP offload documentation Aurelien Aptel
2023-11-22 13:48 ` [PATCH v20 10/20] net/mlx5e: Rename from tls to transport static params Aurelien Aptel
2023-11-22 13:48 ` [PATCH v20 11/20] net/mlx5e: Refactor ico sq polling to get budget Aurelien Aptel
2023-11-22 13:48 ` [PATCH v20 12/20] net/mlx5: Add NVMEoTCP caps, HW bits, 128B CQE and enumerations Aurelien Aptel
2023-11-22 13:48 ` [PATCH v20 13/20] net/mlx5e: NVMEoTCP, offload initialization Aurelien Aptel
2023-11-22 13:48 ` [PATCH v20 14/20] net/mlx5e: TCP flow steering for nvme-tcp acceleration Aurelien Aptel
2023-11-22 13:48 ` [PATCH v20 15/20] net/mlx5e: NVMEoTCP, use KLM UMRs for buffer registration Aurelien Aptel
2023-11-22 13:48 ` [PATCH v20 16/20] net/mlx5e: NVMEoTCP, queue init/teardown Aurelien Aptel
2023-11-22 13:48 ` [PATCH v20 17/20] net/mlx5e: NVMEoTCP, ddp setup and resync Aurelien Aptel
2023-11-22 13:48 ` [PATCH v20 18/20] net/mlx5e: NVMEoTCP, async ddp invalidation Aurelien Aptel
2023-11-22 13:48 ` [PATCH v20 19/20] net/mlx5e: NVMEoTCP, data-path for DDP+DDGST offload Aurelien Aptel
2023-11-22 13:48 ` [PATCH v20 20/20] net/mlx5e: NVMEoTCP, statistics Aurelien Aptel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=253jzq0irx5.fsf@nvidia.com \
--to=aaptel@nvidia.com \
--cc=aurelien.aptel@gmail.com \
--cc=axboe@fb.com \
--cc=borisp@nvidia.com \
--cc=chaitanyak@nvidia.com \
--cc=davem@davemloft.net \
--cc=galshalom@nvidia.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=malin1024@gmail.com \
--cc=mgurtovoy@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@nvidia.com \
--cc=sagi@grimberg.me \
--cc=smalin@nvidia.com \
--cc=yorayz@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).