mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yangyu Chen <cyy@cyyself.name>
To: Sukhdeep Singh <sukhdeeps@marvell.com>,
	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>
Cc: Mina Almasry <almasrymina@google.com>,
	Jesper Dangaard Brouer <hawk@kernel.org>,
	Richard Cochran <richardcochran@gmail.com>,
	Lino Sanfilippo <LinoSanfilippo@gmx.de>,
	Igor Russkikh <irusskikh@marvell.com>,
	Simon Horman <horms@kernel.org>,
	netdev@vger.kernel.org, bpf@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Yangyu Chen <cyy@cyyself.name>
Subject: [PATCH net-next v2 0/3] net: atlantic: convert RX path to page_pool
Date: Fri, 24 Jul 2026 17:00:30 +0800	[thread overview]
Message-ID: <tencent_1F173E0FC1606D2AC704DC9C98AF10984607@qq.com> (raw)

The first two patches are standalone fixes for long-standing ring
teardown leaks and carry Cc: stable tags with their affected ranges
(patch 1: v4.11+, patch 2: v5.2+). They apply and were build- and
runtime-tested independently of each other and of the conversion in
patch 3, which is net-next material only and not tagged for stable.
Backports of patch 1 to trees without XDP support (before v5.19) only
need the xdp_frame branch dropped.

On systems where the NIC sits behind an IOMMU, the atlantic RX path
may not reach line rate: every RX buffer is allocated with
dev_alloc_pages() and mapped with dma_map_page(), then unmapped and
freed once the stack has consumed the packet. Every map/unmap is an
IOTLB/pagetable operation, and depending on the IOMMU this can
dominate the RX path at 10G rates. On an AMD Strix Halo system with a
Thunderbolt-attached QNAP QNA-T310G1S (MTU 1500, TCP over IPv6,
iperf3 -R), RX tops out at about 2.2 Gbit/s.

An earlier patch [1] worked around this by making the RX page order
tunable via a module parameter, amortizing one map/unmap over eight
pages worth of frames. The review feedback was to convert the driver
to the page_pool API instead of adding a knob. This series does that
conversion.

Patches 1 and 2 fix two long-standing teardown leaks first: TX
buffers stranded beyond the budgeted single aq_ring_tx_clean() pass
or past the frozen hw_head, and RX pages parked in consumed but not
yet refilled slots that the bounded deinit walk never visited. Both
are silent leaks today; after the conversion each stranded buffer
would hold a page_pool fragment reference and turn every interface
down into a permanently stalled pool shutdown (reproduction logs are
in the notes of both patches), so they need fixing before the
conversion lands.

Patch 3 converts the RX path to page_pool with the fragment API.
Pages are DMA-mapped once when they enter the per-ring pool
(PP_FLAG_DMA_MAP) and stay mapped while they recycle between the
driver and the stack, so steady-state RX performs no IOMMU work.
page_pool_dev_alloc_frag() takes over the sub-page splitting the
driver's hand-rolled "page flip" scheme did based on page_ref_count(),
buffer ownership becomes transfer-based, and the XDP memory model
switches to MEM_TYPE_PAGE_POOL. The diff is generated with
--histogram so the removed per-page helpers show as whole-function
deletions and aq_get_rxpages() as an in-place rewrite.

Performance, QNA-T310G1S (AQC100) behind Thunderbolt/IOMMU, MTU 1500,
TCP over IPv6, iperf3 -R:

  before:  2.24 Gbit/s
  after:   9.14 Gbit/s

matching what previously required the rxpageorder=3 workaround, but
with order-0 pages and no tunable.

Tested on the same setup: line rate with plain RX and with XDP_PASS;
XDP_TX with a MAC-swap reflector under sustained traffic; repeated
ifdown/ifup and module unload cycles under both plain RX and XDP_TX
load complete without "stalled pool shutdown" warnings or other splats.

Changes in v2 (thanks to Mina Almasry for the review):
 - split the RX deinit gap leak out of the conversion into its own
   fix (patch 2) and generate the conversion diff with --histogram so
   it reads as whole-function removals plus an in-place
   aq_get_rxpages() rewrite
 - add Cc: stable tags with the affected ranges to patches 1 and 2
 - comment the ring-before-rxq-registration ordering and its error
   unwind in aq_vec_ring_alloc()
 - aq_ring_tx_deinit(): return early instead of goto, drop the
   likely()/unlikely() annotations
 - aq_ptp_ring_alloc(): use the err_exit_xdp_rxq label instead of
   open-coding the unregister in the memory model error path
 - rebase on current net-next

[1] https://lore.kernel.org/lkml/tencent_E71C2F71D9631843941A5DF87204D1B5B509@qq.com/

v1: https://lore.kernel.org/lkml/tencent_7DB01BE7F8FA056BB5F11D3570CF636C4309@qq.com/

Yangyu Chen (3):
  net: atlantic: free stranded TX buffers on ring deinit
  net: atlantic: free RX pages of consumed but not refilled buffers
  net: atlantic: convert RX path to page_pool

 drivers/net/ethernet/aquantia/Kconfig         |   1 +
 .../ethernet/aquantia/atlantic/aq_ethtool.c   |   3 -
 .../net/ethernet/aquantia/atlantic/aq_ptp.c   |  18 +-
 .../net/ethernet/aquantia/atlantic/aq_ring.c  | 261 +++++++++---------
 .../net/ethernet/aquantia/atlantic/aq_ring.h  |   7 +-
 .../net/ethernet/aquantia/atlantic/aq_vec.c   |  23 +-
 6 files changed, 169 insertions(+), 144 deletions(-)


base-commit: 89d8006259b81dd25c962f6cc8d7ab268d6ea426
-- 
2.47.3


             reply	other threads:[~2026-07-24  9:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24  9:00 Yangyu Chen [this message]
2026-07-24  9:01 ` [PATCH net-next v2 1/3] net: atlantic: free stranded TX buffers on ring deinit Yangyu Chen
2026-07-24 12:57   ` [EXTERNAL] " Sukhdeep Soni [C]
2026-07-30 10:13   ` Paolo Abeni
2026-07-24  9:02 ` [PATCH net-next v2 2/3] net: atlantic: free RX pages of consumed but not refilled buffers Yangyu Chen
2026-07-24 13:01   ` [EXTERNAL] " Sukhdeep Soni [C]
2026-07-24  9:02 ` [PATCH net-next v2 3/3] net: atlantic: convert RX path to page_pool Yangyu Chen
2026-07-24 13:37   ` [EXTERNAL] " Sukhdeep Soni [C]

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=tencent_1F173E0FC1606D2AC704DC9C98AF10984607@qq.com \
    --to=cyy@cyyself.name \
    --cc=LinoSanfilippo@gmx.de \
    --cc=almasrymina@google.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=horms@kernel.org \
    --cc=irusskikh@marvell.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=richardcochran@gmail.com \
    --cc=stable@vger.kernel.org \
    --cc=sukhdeeps@marvell.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®