public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Aurelien Aptel <aaptel@nvidia.com>,
	linux-nvme@lists.infradead.org, netdev@vger.kernel.org,
	sagi@grimberg.me, hch@lst.de, kbusch@kernel.org, axboe@fb.com,
	chaitanyak@nvidia.com, davem@davemloft.net, kuba@kernel.org
Cc: aurelien.aptel@gmail.com, smalin@nvidia.com, malin1024@gmail.com,
	ogerlitz@nvidia.com, yorayz@nvidia.com, borisp@nvidia.com,
	galshalom@nvidia.com, mgurtovoy@nvidia.com, tariqt@nvidia.com,
	gus@collabora.com, viro@zeniv.linux.org.uk,
	akpm@linux-foundation.org
Subject: Re: [PATCH v30 03/20] iov_iter: skip copy if src == dst for direct data placement
Date: Tue, 15 Jul 2025 09:06:41 -0600	[thread overview]
Message-ID: <59fd61cc-4755-4619-bdb2-6b2091abf002@kernel.dk> (raw)
In-Reply-To: <20250715132750.9619-4-aaptel@nvidia.com>

On 7/15/25 7:27 AM, Aurelien Aptel wrote:
> From: Ben Ben-Ishay <benishay@nvidia.com>
> 
> When using direct data placement (DDP) the NIC could write the payload
> directly into the destination buffer and constructs SKBs such that
> they point to this data. To skip copies when SKB data already resides
> in the destination buffer we check if (src == dst), and skip the copy
> when it's true.
> 
> Signed-off-by: Ben Ben-Ishay <benishay@nvidia.com>
> Signed-off-by: Boris Pismenny <borisp@nvidia.com>
> Signed-off-by: Or Gerlitz <ogerlitz@nvidia.com>
> Signed-off-by: Yoray Zack <yorayz@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>
> Reviewed-by: Max Gurtovoy <mgurtovoy@nvidia.com>
> ---
>  lib/iov_iter.c | 9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)
> 
> diff --git a/lib/iov_iter.c b/lib/iov_iter.c
> index f9193f952f49..47fdb32653a2 100644
> --- a/lib/iov_iter.c
> +++ b/lib/iov_iter.c
> @@ -62,7 +62,14 @@ static __always_inline
>  size_t memcpy_to_iter(void *iter_to, size_t progress,
>  		      size_t len, void *from, void *priv2)
>  {
> -	memcpy(iter_to, from + progress, len);
> +	/*
> +	 * When using direct data placement (DDP) the hardware writes
> +	 * data directly to the destination buffer, and constructs
> +	 * IOVs such that they point to this data.
> +	 * Thus, when the src == dst we skip the memcpy.
> +	 */
> +	if (!(IS_ENABLED(CONFIG_ULP_DDP) && iter_to == from + progress))
> +		memcpy(iter_to, from + progress, len);
>  	return 0;
>  }

This seems like entirely the wrong place to apply this logic...

-- 
Jens Axboe

  reply	other threads:[~2025-07-15 15:06 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15 13:27 [PATCH v30 00/20] nvme-tcp receive offloads Aurelien Aptel
2025-07-15 13:27 ` [PATCH v30 01/20] net: Introduce direct data placement tcp offload Aurelien Aptel
2025-07-15 13:27 ` [PATCH v30 02/20] netlink: add new family to manage ULP_DDP enablement and stats Aurelien Aptel
2025-07-15 13:27 ` [PATCH v30 03/20] iov_iter: skip copy if src == dst for direct data placement Aurelien Aptel
2025-07-15 15:06   ` Jens Axboe [this message]
2025-07-15 17:08     ` Chaitanya Kulkarni
2025-07-15 17:14       ` Jens Axboe
2025-07-25 16:22     ` Aurelien Aptel
2025-07-31 13:29       ` Jens Axboe
2025-07-15 13:27 ` [PATCH v30 04/20] net/tls,core: export get_netdev_for_sock Aurelien Aptel
2025-07-15 13:27 ` [PATCH v30 05/20] nvme-tcp: Add DDP offload control path Aurelien Aptel
2025-07-15 13:27 ` [PATCH v30 06/20] nvme-tcp: Add DDP data-path Aurelien Aptel
2025-07-15 13:27 ` [PATCH v30 07/20] nvme-tcp: RX DDGST offload Aurelien Aptel
2025-07-15 13:27 ` [PATCH v30 08/20] nvme-tcp: Deal with netdevice DOWN events Aurelien Aptel
2025-07-15 13:27 ` [PATCH v30 09/20] Documentation: add ULP DDP offload documentation Aurelien Aptel
2025-07-15 13:27 ` [PATCH v30 10/20] net/mlx5e: Rename from tls to transport static params Aurelien Aptel
2025-07-15 13:27 ` [PATCH v30 11/20] net/mlx5e: Refactor ico sq polling to get budget Aurelien Aptel
2025-07-15 13:27 ` [PATCH v30 12/20] net/mlx5: Add NVMEoTCP caps, HW bits, 128B CQE and enumerations Aurelien Aptel
2025-07-15 13:27 ` [PATCH v30 13/20] net/mlx5e: NVMEoTCP, offload initialization Aurelien Aptel
2025-07-15 13:27 ` [PATCH v30 14/20] net/mlx5e: TCP flow steering for nvme-tcp acceleration Aurelien Aptel
2025-07-15 13:27 ` [PATCH v30 15/20] net/mlx5e: NVMEoTCP, use KLM UMRs for buffer registration Aurelien Aptel
2025-07-15 13:27 ` [PATCH v30 16/20] net/mlx5e: NVMEoTCP, queue init/teardown Aurelien Aptel
2025-07-15 13:27 ` [PATCH v30 17/20] net/mlx5e: NVMEoTCP, ddp setup and resync Aurelien Aptel
2025-07-15 13:27 ` [PATCH v30 18/20] net/mlx5e: NVMEoTCP, async ddp invalidation Aurelien Aptel
2025-07-15 13:27 ` [PATCH v30 19/20] net/mlx5e: NVMEoTCP, data-path for DDP+DDGST offload Aurelien Aptel
2025-07-15 13:27 ` [PATCH v30 20/20] net/mlx5e: NVMEoTCP, statistics Aurelien Aptel
2025-07-31 12:40 ` [PATCH v30 00/20] nvme-tcp receive offloads Aurelien Aptel
2025-07-31 14:20   ` Jakub Kicinski

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=59fd61cc-4755-4619-bdb2-6b2091abf002@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=aaptel@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --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=gus@collabora.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=tariqt@nvidia.com \
    --cc=viro@zeniv.linux.org.uk \
    --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