public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Aurelien Aptel <aaptel@nvidia.com>
To: 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: Ben Ben-Ishay <benishay@nvidia.com>,
	aaptel@nvidia.com, 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
Subject: [PATCH v13 05/24] iov_iter: skip copy if src == dst for direct data placement
Date: Tue, 22 Aug 2023 15:04:06 +0000	[thread overview]
Message-ID: <20230822150425.3390-6-aaptel@nvidia.com> (raw)
In-Reply-To: <20230822150425.3390-1-aaptel@nvidia.com>

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>
---
 lib/iov_iter.c | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/lib/iov_iter.c b/lib/iov_iter.c
index e4dc809d1075..f01ee0e28295 100644
--- a/lib/iov_iter.c
+++ b/lib/iov_iter.c
@@ -313,9 +313,15 @@ size_t _copy_to_iter(const void *addr, size_t bytes, struct iov_iter *i)
 		return 0;
 	if (user_backed_iter(i))
 		might_fault();
+	/*
+	 * 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.
+	 */
 	iterate_and_advance(i, bytes, base, len, off,
 		copyout(base, addr + off, len),
-		memcpy(base, addr + off, len)
+		(base != addr + off) && memcpy(base, addr + off, len)
 	)
 
 	return bytes;
-- 
2.34.1



  parent reply	other threads:[~2023-08-22 15:05 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22 15:04 [PATCH v13 00/24] nvme-tcp receive offloads Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 01/24] net: Introduce direct data placement tcp offload Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 02/24] net/ethtool: add new stringset ETH_SS_ULP_DDP_{CAPS,STATS} Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 03/24] net/ethtool: add ULP_DDP_{GET,SET} operations for caps and stats Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 04/24] Documentation: document netlink ULP_DDP_GET/SET messages Aurelien Aptel
2023-08-22 15:04 ` Aurelien Aptel [this message]
2023-08-22 15:04 ` [PATCH v13 06/24] net/tls,core: export get_netdev_for_sock Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 07/24] nvme-tcp: Add DDP offload control path Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 08/24] nvme-tcp: Add DDP data-path Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 09/24] nvme-tcp: RX DDGST offload Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 10/24] nvme-tcp: Deal with netdevice DOWN events Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 11/24] Documentation: add ULP DDP offload documentation Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 12/24] net/mlx5e: Rename from tls to transport static params Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 13/24] net/mlx5e: Refactor ico sq polling to get budget Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 14/24] net/mlx5e: Have mdev pointer directly on the icosq structure Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 15/24] net/mlx5e: Refactor doorbell function to allow avoiding a completion Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 16/24] net/mlx5: Add NVMEoTCP caps, HW bits, 128B CQE and enumerations Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 17/24] net/mlx5e: NVMEoTCP, offload initialization Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 18/24] net/mlx5e: TCP flow steering for nvme-tcp acceleration Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 19/24] net/mlx5e: NVMEoTCP, use KLM UMRs for buffer registration Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 20/24] net/mlx5e: NVMEoTCP, queue init/teardown Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 21/24] net/mlx5e: NVMEoTCP, ddp setup and resync Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 22/24] net/mlx5e: NVMEoTCP, async ddp invalidation Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 23/24] net/mlx5e: NVMEoTCP, data-path for DDP+DDGST offload Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 24/24] net/mlx5e: NVMEoTCP, statistics Aurelien Aptel
2023-08-24  2:02 ` [PATCH v13 00/24] nvme-tcp receive offloads 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=20230822150425.3390-6-aaptel@nvidia.com \
    --to=aaptel@nvidia.com \
    --cc=aurelien.aptel@gmail.com \
    --cc=axboe@fb.com \
    --cc=benishay@nvidia.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