From: Max Gurtovoy <mgurtovoy@nvidia.com>
To: Aurelien Aptel <aaptel@nvidia.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"sagi@grimberg.me" <sagi@grimberg.me>, "hch@lst.de" <hch@lst.de>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"axboe@fb.com" <axboe@fb.com>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>
Cc: Yoray Zack <yorayz@nvidia.com>,
"aurelien.aptel@gmail.com" <aurelien.aptel@gmail.com>,
Shai Malin <smalin@nvidia.com>,
"malin1024@gmail.com" <malin1024@gmail.com>,
Or Gerlitz <ogerlitz@nvidia.com>,
Boris Pismenny <borisp@nvidia.com>,
Gal Shalom <galshalom@nvidia.com>
Subject: Re: [PATCH v21 07/20] nvme-tcp: RX DDGST offload
Date: Wed, 20 Dec 2023 15:35:20 +0200 [thread overview]
Message-ID: <5c6039e6-e373-4e38-9e45-7834551be4d0@nvidia.com> (raw)
In-Reply-To: <20231214132623.119227-8-aaptel@nvidia.com>
On 14/12/2023 15:26, Aurelien Aptel wrote:
> From: Yoray Zack <yorayz@nvidia.com>
>
> Enable rx side of DDGST offload when supported.
>
> At the end of the capsule, check if all the skb bits are on, and if not
> recalculate the DDGST in SW and check it.
>
> Signed-off-by: Yoray Zack <yorayz@nvidia.com>
> Signed-off-by: Boris Pismenny <borisp@nvidia.com>
> Signed-off-by: Ben Ben-Ishay <benishay@nvidia.com>
> Signed-off-by: Or Gerlitz <ogerlitz@nvidia.com>
> Signed-off-by: Shai Malin <smalin@nvidia.com>
> Signed-off-by: Aurelien Aptel <aaptel@nvidia.com>
> Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
> ---
> drivers/nvme/host/tcp.c | 81 ++++++++++++++++++++++++++++++++++++++---
> 1 file changed, 76 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/nvme/host/tcp.c b/drivers/nvme/host/tcp.c
> index 09ffa8ba7e72..a7591eb90b96 100644
> --- a/drivers/nvme/host/tcp.c
> +++ b/drivers/nvme/host/tcp.c
> @@ -143,6 +143,7 @@ enum nvme_tcp_queue_flags {
> NVME_TCP_Q_LIVE = 1,
> NVME_TCP_Q_POLLING = 2,
> NVME_TCP_Q_OFF_DDP = 3,
> + NVME_TCP_Q_OFF_DDGST_RX = 4,
> };
>
> enum nvme_tcp_recv_state {
> @@ -180,6 +181,7 @@ struct nvme_tcp_queue {
> * is pending (ULP_DDP_RESYNC_PENDING).
> */
> atomic64_t resync_tcp_seq;
> + bool ddp_ddgst_valid;
> #endif
>
> /* send state */
> @@ -378,6 +380,30 @@ nvme_tcp_get_ddp_netdev_with_limits(struct nvme_tcp_ctrl *ctrl)
> return NULL;
> }
>
> +static inline bool nvme_tcp_ddp_ddgst_ok(struct nvme_tcp_queue *queue)
> +{
> + return queue->ddp_ddgst_valid;
> +}
> +
> +static inline void nvme_tcp_ddp_ddgst_update(struct nvme_tcp_queue *queue,
> + struct sk_buff *skb)
> +{
> + if (queue->ddp_ddgst_valid)
> + queue->ddp_ddgst_valid = skb_is_ulp_crc(skb);
> +}
> +
> +static void nvme_tcp_ddp_ddgst_recalc(struct ahash_request *hash,
> + struct request *rq,
> + __le32 *ddgst)
> +{
> + struct nvme_tcp_request *req;
> +
> + 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 = {
> @@ -467,6 +493,10 @@ static int nvme_tcp_offload_socket(struct nvme_tcp_queue *queue)
> return ret;
>
> set_bit(NVME_TCP_Q_OFF_DDP, &queue->flags);
> + if (queue->data_digest &&
> + ulp_ddp_is_cap_active(queue->ctrl->ddp_netdev,
> + ULP_DDP_CAP_NVME_TCP_DDGST_RX))
> + set_bit(NVME_TCP_Q_OFF_DDGST_RX, &queue->flags);
>
> return 0;
> }
> @@ -474,6 +504,7 @@ static int nvme_tcp_offload_socket(struct nvme_tcp_queue *queue)
> static void nvme_tcp_unoffload_socket(struct nvme_tcp_queue *queue)
> {
> clear_bit(NVME_TCP_Q_OFF_DDP, &queue->flags);
> + clear_bit(NVME_TCP_Q_OFF_DDGST_RX, &queue->flags);
> ulp_ddp_sk_del(queue->ctrl->ddp_netdev, queue->sock->sk);
> }
>
> @@ -582,6 +613,20 @@ static void nvme_tcp_resync_response(struct nvme_tcp_queue *queue,
> struct sk_buff *skb, unsigned int offset)
> {}
>
> +static inline bool nvme_tcp_ddp_ddgst_ok(struct nvme_tcp_queue *queue)
> +{
> + return false;
> +}
> +
> +static inline void nvme_tcp_ddp_ddgst_update(struct nvme_tcp_queue *queue,
> + struct sk_buff *skb)
> +{}
> +
> +static void nvme_tcp_ddp_ddgst_recalc(struct ahash_request *hash,
> + struct request *rq,
> + __le32 *ddgst)
> +{}
> +
> #endif
>
> static void nvme_tcp_init_iter(struct nvme_tcp_request *req,
> @@ -842,6 +887,9 @@ static void nvme_tcp_init_recv_ctx(struct nvme_tcp_queue *queue)
> queue->pdu_offset = 0;
> queue->data_remaining = -1;
> queue->ddgst_remaining = 0;
> +#ifdef CONFIG_ULP_DDP
> + queue->ddp_ddgst_valid = true;
> +#endif
> }
>
> static void nvme_tcp_error_recovery(struct nvme_ctrl *ctrl)
> @@ -1107,6 +1155,10 @@ static int nvme_tcp_recv_data(struct nvme_tcp_queue *queue, struct sk_buff *skb,
> nvme_cid_to_rq(nvme_tcp_tagset(queue), pdu->command_id);
> struct nvme_tcp_request *req = blk_mq_rq_to_pdu(rq);
>
> + if (queue->data_digest &&
> + test_bit(NVME_TCP_Q_OFF_DDGST_RX, &queue->flags))
> + nvme_tcp_ddp_ddgst_update(queue, skb);
I think we can only use the test_bit(NVME_TCP_Q_OFF_DDGST_RX,
&queue->flags) in the if condition.
We dont set this bit unless queue->data_digest is true, correct ?
It is a micro optimization, but still can help.
Otherwise looks good,
Reviewed-by: Max Gurtovoy <mgurtovoy@nvidia.com>
> +
> while (true) {
> int recv_len, ret;
>
> @@ -1135,7 +1187,8 @@ static int nvme_tcp_recv_data(struct nvme_tcp_queue *queue, struct sk_buff *skb,
> recv_len = min_t(size_t, recv_len,
> iov_iter_count(&req->iter));
>
> - if (queue->data_digest)
> + if (queue->data_digest &&
> + !test_bit(NVME_TCP_Q_OFF_DDGST_RX, &queue->flags))
> ret = skb_copy_and_hash_datagram_iter(skb, *offset,
> &req->iter, recv_len, queue->rcv_hash);
> else
> @@ -1177,8 +1230,11 @@ static int nvme_tcp_recv_ddgst(struct nvme_tcp_queue *queue,
> char *ddgst = (char *)&queue->recv_ddgst;
> size_t recv_len = min_t(size_t, *len, queue->ddgst_remaining);
> off_t off = NVME_TCP_DIGEST_LENGTH - queue->ddgst_remaining;
> + struct request *rq;
> int ret;
>
> + if (test_bit(NVME_TCP_Q_OFF_DDGST_RX, &queue->flags))
> + nvme_tcp_ddp_ddgst_update(queue, skb);
> ret = skb_copy_bits(skb, *offset, &ddgst[off], recv_len);
> if (unlikely(ret))
> return ret;
> @@ -1189,9 +1245,25 @@ static int nvme_tcp_recv_ddgst(struct nvme_tcp_queue *queue,
> if (queue->ddgst_remaining)
> return 0;
>
> + rq = nvme_cid_to_rq(nvme_tcp_tagset(queue),
> + pdu->command_id);
> +
> + if (test_bit(NVME_TCP_Q_OFF_DDGST_RX, &queue->flags)) {
> + /*
> + * If HW successfully offloaded the digest
> + * verification, we can skip it
> + */
> + if (nvme_tcp_ddp_ddgst_ok(queue))
> + goto out;
> + /*
> + * Otherwise we have to recalculate and verify the
> + * digest with the software-fallback
> + */
> + nvme_tcp_ddp_ddgst_recalc(queue->rcv_hash, rq,
> + &queue->exp_ddgst);
> + }
> +
> if (queue->recv_ddgst != queue->exp_ddgst) {
> - struct request *rq = nvme_cid_to_rq(nvme_tcp_tagset(queue),
> - pdu->command_id);
> struct nvme_tcp_request *req = blk_mq_rq_to_pdu(rq);
>
> req->status = cpu_to_le16(NVME_SC_DATA_XFER_ERROR);
> @@ -1202,9 +1274,8 @@ static int nvme_tcp_recv_ddgst(struct nvme_tcp_queue *queue,
> le32_to_cpu(queue->exp_ddgst));
> }
>
> +out:
> if (pdu->hdr.flags & NVME_TCP_F_DATA_SUCCESS) {
> - struct request *rq = nvme_cid_to_rq(nvme_tcp_tagset(queue),
> - pdu->command_id);
> struct nvme_tcp_request *req = blk_mq_rq_to_pdu(rq);
>
> nvme_tcp_end_request(rq, le16_to_cpu(req->status));
next prev parent reply other threads:[~2023-12-20 13:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 13:26 [PATCH v21 00/20] nvme-tcp receive offloads Aurelien Aptel
2023-12-14 13:26 ` [PATCH v21 01/20] net: Introduce direct data placement tcp offload Aurelien Aptel
2023-12-14 13:26 ` [PATCH v21 02/20] netlink: add new family to manage ULP_DDP enablement and stats Aurelien Aptel
2023-12-14 13:26 ` [PATCH v21 03/20] iov_iter: skip copy if src == dst for direct data placement Aurelien Aptel
2023-12-14 13:26 ` [PATCH v21 04/20] net/tls,core: export get_netdev_for_sock Aurelien Aptel
2023-12-15 2:11 ` Jakub Kicinski
2023-12-15 13:46 ` Aurelien Aptel
2023-12-14 13:26 ` [PATCH v21 05/20] nvme-tcp: Add DDP offload control path Aurelien Aptel
2023-12-17 0:18 ` Max Gurtovoy
2023-12-18 20:00 ` Aurelien Aptel
2023-12-20 11:30 ` Max Gurtovoy
2023-12-14 13:26 ` [PATCH v21 06/20] nvme-tcp: Add DDP data-path Aurelien Aptel
2023-12-17 17:06 ` Max Gurtovoy
2023-12-18 18:08 ` Aurelien Aptel
2023-12-18 18:47 ` Max Gurtovoy
2023-12-14 13:26 ` [PATCH v21 07/20] nvme-tcp: RX DDGST offload Aurelien Aptel
2023-12-20 13:35 ` Max Gurtovoy [this message]
2023-12-14 13:26 ` [PATCH v21 08/20] nvme-tcp: Deal with netdevice DOWN events Aurelien Aptel
2023-12-14 13:26 ` [PATCH v21 09/20] Documentation: add ULP DDP offload documentation Aurelien Aptel
2023-12-14 13:26 ` [PATCH v21 10/20] net/mlx5e: Rename from tls to transport static params Aurelien Aptel
2023-12-14 13:26 ` [PATCH v21 11/20] net/mlx5e: Refactor ico sq polling to get budget Aurelien Aptel
2023-12-14 13:26 ` [PATCH v21 12/20] net/mlx5: Add NVMEoTCP caps, HW bits, 128B CQE and enumerations Aurelien Aptel
2023-12-14 13:26 ` [PATCH v21 13/20] net/mlx5e: NVMEoTCP, offload initialization Aurelien Aptel
2023-12-14 13:26 ` [PATCH v21 14/20] net/mlx5e: TCP flow steering for nvme-tcp acceleration Aurelien Aptel
2023-12-14 13:26 ` [PATCH v21 15/20] net/mlx5e: NVMEoTCP, use KLM UMRs for buffer registration Aurelien Aptel
2023-12-14 13:26 ` [PATCH v21 16/20] net/mlx5e: NVMEoTCP, queue init/teardown Aurelien Aptel
2023-12-14 13:26 ` [PATCH v21 17/20] net/mlx5e: NVMEoTCP, ddp setup and resync Aurelien Aptel
2023-12-14 13:26 ` [PATCH v21 18/20] net/mlx5e: NVMEoTCP, async ddp invalidation Aurelien Aptel
2023-12-14 13:26 ` [PATCH v21 19/20] net/mlx5e: NVMEoTCP, data-path for DDP+DDGST offload Aurelien Aptel
2023-12-14 13:26 ` [PATCH v21 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=5c6039e6-e373-4e38-9e45-7834551be4d0@nvidia.com \
--to=mgurtovoy@nvidia.com \
--cc=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=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