From: Jakub Kicinski <kuba@kernel.org>
To: wei.fang@nxp.com
Cc: Jakub Kicinski <kuba@kernel.org>,
ast@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
pabeni@redhat.com, xiaoning.wang@nxp.com,
john.fastabend@gmail.com, daniel@iogearbox.net, sdf@fomichev.me,
frank.li@nxp.com, linux-kernel@vger.kernel.org, hawk@kernel.org,
horms@kernel.org, bpf@vger.kernel.org, edumazet@google.com,
netdev@vger.kernel.org, imx@lists.linux.dev,
shenwei.wang@nxp.com
Subject: Re: [v6,net-next,15/15] net: fec: add AF_XDP zero-copy support
Date: Wed, 4 Feb 2026 21:28:39 -0800 [thread overview]
Message-ID: <20260205052839.2449416-1-kuba@kernel.org> (raw)
In-Reply-To: <20260203052329.1085444-16-wei.fang@nxp.com>
This is an AI-generated review of your patch. The human sending this
email has considered the AI review valid, or at least plausible.
For local reproduction steps see https://netdev-ai.bots.linux.dev/ai-local.html
---
net: fec: add AF_XDP zero-copy support
This commit adds AF_XDP zero-copy support for both TX and RX on the FEC
Ethernet driver. It introduces new functions for XSK buffer allocation,
RX/TX queue processing in zero-copy mode, and XSK pool setup/teardown.
> For TX, there are two cases, one is the frames from the AF_XDP socket,
> so fec_enet_xsk_xmit() is added to directly transmit the frames from
> the socket and the buffer type is marked as FEC_TXBUF_T_XSK_XMIT. The
> other one is the frams from the RX queue (XDP_TX action), the buffer
This isn't a bug, but "frams" should be "frames".
> diff --git a/drivers/net/ethernet/freescale/fec_main.c b/drivers/net/ethernet/freescale/fec_main.c
> --- a/drivers/net/ethernet/freescale/fec_main.c
> +++ b/drivers/net/ethernet/freescale/fec_main.c
[ ... ]
> +static int fec_enet_xsk_tx_xmit(struct fec_enet_private *fep,
> + struct xdp_buff *xsk, int cpu,
> + int queue)
> +{
[ ... ]
> + bdp->cbd_bufaddr = cpu_to_fec32(dma);
> + bdp->cbd_datlen = cpu_to_fec16(len);
> +
> + if (fep->bufdesc_ex) {
> + struct bufdesc_ex *ebdp = (struct bufdesc_ex *)bdp;
> +
> + if (fep->quirks & FEC_QUIRK_HAS_AVB)
> + estatus |= FEC_TX_BD_FTYPE(txq->bd.qid);
> +
> + ebdp->cbd_bdu = 0;
> + ebdp->cbd_esc = cpu_to_fec32(estatus);
> + }
> +
> + status |= (BD_ENET_TX_READY | BD_ENET_TX_TC);
> + bdp->cbd_sc = cpu_to_fec16(status);
> + dma_wmb();
Is there a missing dma_wmb() before setting BD_ENET_TX_READY? The
descriptor fields (cbd_bufaddr, cbd_datlen, cbd_esc) are written before
the status, but without a memory barrier, the hardware could see the
READY bit before those fields are visible on weakly-ordered architectures.
Compare to fec_enet_xsk_xmit() in the same file which does:
dma_wmb();
status |= BD_ENET_TX_READY | BD_ENET_TX_TC;
bdp->cbd_sc = cpu_to_fec16(status);
dma_wmb();
The dma_wmb() after setting status only ensures ordering with subsequent
writes (bd.cur update), not with the preceding descriptor field writes.
next prev parent reply other threads:[~2026-02-05 5:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 5:23 [PATCH v6 net-next 00/15] net: fec: improve XDP copy mode and add AF_XDP zero-copy support Wei Fang
2026-02-03 5:23 ` [PATCH v6 net-next 01/15] net: fec: add fec_txq_trigger_xmit() helper Wei Fang
2026-02-03 5:23 ` [PATCH v6 net-next 02/15] net: fec: add fec_rx_error_check() to check RX errors Wei Fang
2026-02-03 5:23 ` [PATCH v6 net-next 03/15] net: fec: add rx_shift to indicate the extra bytes padded in front of RX frame Wei Fang
2026-02-03 5:23 ` [PATCH v6 net-next 04/15] net: fec: add fec_build_skb() to build a skb Wei Fang
2026-02-03 5:23 ` [PATCH v6 net-next 05/15] net: fec: improve fec_enet_rx_queue() Wei Fang
2026-02-03 5:23 ` [PATCH v6 net-next 06/15] net: fec: add fec_enet_rx_queue_xdp() for XDP path Wei Fang
2026-02-05 5:28 ` [v6,net-next,06/15] " Jakub Kicinski
2026-02-05 6:16 ` Wei Fang
2026-02-03 5:23 ` [PATCH v6 net-next 07/15] net: fec: add tx_qid parameter to fec_enet_xdp_tx_xmit() Wei Fang
2026-02-03 5:23 ` [PATCH v6 net-next 08/15] net: fec: transmit XDP frames in bulk Wei Fang
2026-02-03 5:23 ` [PATCH v6 net-next 09/15] net: fec: remove unnecessary NULL pointer check when clearing TX BD ring Wei Fang
2026-02-03 5:23 ` [PATCH v6 net-next 10/15] net: fec: use switch statement to check the type of tx_buf Wei Fang
2026-02-03 5:23 ` [PATCH v6 net-next 11/15] net: fec: remove the size parameter from fec_enet_create_page_pool() Wei Fang
2026-02-03 5:23 ` [PATCH v6 net-next 12/15] net: fec: move xdp_rxq_info* APIs out of fec_enet_create_page_pool() Wei Fang
2026-02-03 5:23 ` [PATCH v6 net-next 13/15] net: fec: add fec_alloc_rxq_buffers_pp() to allocate buffers from page pool Wei Fang
2026-02-03 5:23 ` [PATCH v6 net-next 14/15] net: fec: improve fec_enet_tx_queue() Wei Fang
2026-02-03 5:23 ` [PATCH v6 net-next 15/15] net: fec: add AF_XDP zero-copy support Wei Fang
2026-02-05 5:28 ` Jakub Kicinski [this message]
2026-02-05 6:04 ` [v6,net-next,15/15] " Wei Fang
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=20260205052839.2449416-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=frank.li@nxp.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=imx@lists.linux.dev \
--cc=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shenwei.wang@nxp.com \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@nxp.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