From: Mark Bloch <mbloch@nvidia.com>
To: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
Simon Horman <horms@kernel.org>
Cc: <saeedm@nvidia.com>, <gal@nvidia.com>, <leonro@nvidia.com>,
<tariqt@nvidia.com>, Leon Romanovsky <leon@kernel.org>,
"Jesper Dangaard Brouer" <hawk@kernel.org>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Richard Cochran <richardcochran@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
Stanislav Fomichev <sdf@fomichev.me>, <netdev@vger.kernel.org>,
<linux-rdma@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<bpf@vger.kernel.org>, Dragos Tatulea <dtatulea@nvidia.com>,
Mina Almasry <almasrymina@google.com>,
Mark Bloch <mbloch@nvidia.com>
Subject: [PATCH net-next v6 12/12] net/mlx5e: Add TX support for netmems
Date: Mon, 16 Jun 2025 17:14:41 +0300 [thread overview]
Message-ID: <20250616141441.1243044-13-mbloch@nvidia.com> (raw)
In-Reply-To: <20250616141441.1243044-1-mbloch@nvidia.com>
From: Dragos Tatulea <dtatulea@nvidia.com>
Declare netmem TX support in netdev.
As required, use the netmem aware dma unmapping APIs
for unmapping netmems in tx completion path.
Signed-off-by: Dragos Tatulea <dtatulea@nvidia.com>
Reviewed-by: Tariq Toukan <tariqt@nvidia.com>
Reviewed-by: Mina Almasry <almasrymina@google.com>
Signed-off-by: Mark Bloch <mbloch@nvidia.com>
---
drivers/net/ethernet/mellanox/mlx5/core/en/txrx.h | 3 ++-
drivers/net/ethernet/mellanox/mlx5/core/en_main.c | 2 ++
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en/txrx.h b/drivers/net/ethernet/mellanox/mlx5/core/en/txrx.h
index e837c21d3d21..6501252359b0 100644
--- a/drivers/net/ethernet/mellanox/mlx5/core/en/txrx.h
+++ b/drivers/net/ethernet/mellanox/mlx5/core/en/txrx.h
@@ -362,7 +362,8 @@ mlx5e_tx_dma_unmap(struct device *pdev, struct mlx5e_sq_dma *dma)
dma_unmap_single(pdev, dma->addr, dma->size, DMA_TO_DEVICE);
break;
case MLX5E_DMA_MAP_PAGE:
- dma_unmap_page(pdev, dma->addr, dma->size, DMA_TO_DEVICE);
+ netmem_dma_unmap_page_attrs(pdev, dma->addr, dma->size,
+ DMA_TO_DEVICE, 0);
break;
default:
WARN_ONCE(true, "mlx5e_tx_dma_unmap unknown DMA type!\n");
diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
index b4df62b58292..24559cbcbfc2 100644
--- a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
+++ b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
@@ -5741,6 +5741,8 @@ static void mlx5e_build_nic_netdev(struct net_device *netdev)
netdev->priv_flags |= IFF_UNICAST_FLT;
+ netdev->netmem_tx = true;
+
netif_set_tso_max_size(netdev, GSO_MAX_SIZE);
mlx5e_set_xdp_feature(netdev);
mlx5e_set_netdev_dev_addr(netdev);
--
2.34.1
next prev parent reply other threads:[~2025-06-16 14:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 14:14 [PATCH net-next v6 00/12] net/mlx5e: Add support for devmem and io_uring TCP zero-copy Mark Bloch
2025-06-16 14:14 ` [PATCH net-next v6 01/12] net: Allow const args for of page_to_netmem() Mark Bloch
2025-06-16 14:14 ` [PATCH net-next v6 02/12] net: Add skb_can_coalesce for netmem Mark Bloch
2025-06-16 14:14 ` [PATCH net-next v6 03/12] page_pool: Add page_pool_dev_alloc_netmems helper Mark Bloch
2025-06-16 14:14 ` [PATCH net-next v6 04/12] net/mlx5e: SHAMPO: Reorganize mlx5_rq_shampo_alloc Mark Bloch
2025-06-16 14:14 ` [PATCH net-next v6 05/12] net/mlx5e: SHAMPO: Remove redundant params Mark Bloch
2025-06-16 14:14 ` [PATCH net-next v6 06/12] net/mlx5e: SHAMPO: Improve hw gro capability checking Mark Bloch
2025-06-16 14:14 ` [PATCH net-next v6 07/12] net/mlx5e: SHAMPO: Separate pool for headers Mark Bloch
2025-06-16 14:14 ` [PATCH net-next v6 08/12] net/mlx5e: Convert over to netmem Mark Bloch
2025-06-16 14:14 ` [PATCH net-next v6 09/12] net/mlx5e: Add support for UNREADABLE netmem page pools Mark Bloch
2025-06-16 14:14 ` [PATCH net-next v6 10/12] net/mlx5e: Implement queue mgmt ops and single channel swap Mark Bloch
2025-06-16 23:20 ` Mina Almasry
2025-06-18 6:06 ` Zhu Yanjun
2025-06-16 14:14 ` [PATCH net-next v6 11/12] net/mlx5e: Support ethtool tcp-data-split settings Mark Bloch
2025-06-16 14:14 ` Mark Bloch [this message]
2025-06-18 22:16 ` [PATCH net-next v6 12/12] net/mlx5e: Add TX support for netmems Stanislav Fomichev
2025-06-19 7:19 ` Dragos Tatulea
2025-06-19 15:32 ` Mina Almasry
2025-06-19 16:07 ` Dragos Tatulea
2025-06-19 22:19 ` Mina Almasry
2025-06-25 10:57 ` Dragos Tatulea
2025-06-18 2:01 ` [PATCH net-next v6 00/12] net/mlx5e: Add support for devmem and io_uring TCP zero-copy patchwork-bot+netdevbpf
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=20250616141441.1243044-13-mbloch@nvidia.com \
--to=mbloch@nvidia.com \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=saeedm@nvidia.com \
--cc=sdf@fomichev.me \
--cc=tariqt@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
all inboxes | Powered by JetHome®