netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Wei <dw@davidwei.uk>
To: netdev@vger.kernel.org
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: [PATCH net-next v1] iou-zcrx: update documentation
Date: Tue, 19 Aug 2025 13:56:32 -0700	[thread overview]
Message-ID: <20250819205632.1368993-1-dw@davidwei.uk> (raw)

Update io_uring zc rx documentation with:

* Current supported NICs with minimum FW reqs
* Mellanox needs HW GRO explicitly enabled

Signed-off-by: David Wei <dw@davidwei.uk>
---
 Documentation/networking/iou-zcrx.rst | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/Documentation/networking/iou-zcrx.rst b/Documentation/networking/iou-zcrx.rst
index 0127319b30bb..bfc08154e697 100644
--- a/Documentation/networking/iou-zcrx.rst
+++ b/Documentation/networking/iou-zcrx.rst
@@ -41,6 +41,16 @@ RSS
 In addition to flow steering above, RSS is required to steer all other non-zero
 copy flows away from queues that are configured for io_uring ZC Rx.
 
+Supported NICs
+==============
+
+Zero copy Rx currently support two NIC families:
+
+* Broadcom Thor (BCM95750x) family
+  * Minimum FW is 232
+* Mellanox ConnectX-7 (MT2910) family
+  * Minimum FW is 28.42
+
 Usage
 =====
 
@@ -57,6 +67,10 @@ Enable header/data split::
 
   ethtool -G eth0 tcp-data-split on
 
+Enable HW GRO (for Mellanox NICs)::
+
+  ethtool -K eth0 rx-gro-hw on
+
 Carve out half of the HW Rx queues for zero copy using RSS::
 
   ethtool -X eth0 equal 1
-- 
2.47.3


             reply	other threads:[~2025-08-19 20:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-19 20:56 David Wei [this message]
2025-08-21  2:44 ` [PATCH net-next v1] iou-zcrx: update documentation Jakub Kicinski
2025-08-21  4:34 ` Jamal Hadi Salim
2025-08-21 14:21   ` Jakub Kicinski
2025-08-23  4:06     ` Jamal Hadi Salim

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=20250819205632.1368993-1-dw@davidwei.uk \
    --to=dw@davidwei.uk \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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).