From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Machon <daniel.machon@microchip.com>
Cc: horatiu.vultur@microchip.com, UNGLinuxDriver@microchip.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, ast@kernel.org,
daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.com,
sdf@fomichev.me, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH net] net: lan966x: fix the DB dataptr of frames from ndo_xdp_xmit
Date: Tue, 27 Oct 2026 22:30:09 +0000 [thread overview]
Message-ID: <179314020904.360855.3604879146922588076.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261026-lan966x-xdp-xmit-dataptr-v1-1-d0dd068324de@microchip.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 26 Oct 2026 14:46:39 +0100 you wrote:
> lan966x_fdma_xmit_xdpf() transmits both XDP_TX frames and xdp_frames
> from ndo_xdp_xmit, and builds the DB with
> lan966x_fdma_xdp_tx_dataptr_cb(), which adds XDP_PACKET_HEADROOM to the
> stored DMA address.
>
> Before this patch, the headroom is also added for xdp_frames. For
> XDP_TX the stored address is the start of the page pool page, but for an
> xdp_frame it is the mapping of the IFH placed in front of the frame
> data, so frames from ndo_xdp_xmit are read from XDP_PACKET_HEADROOM
> bytes after their IFH.
>
> [...]
Here is the summary with links:
- [net] net: lan966x: fix the DB dataptr of frames from ndo_xdp_xmit
https://git.kernel.org/netdev/net/c/ce3192e0dafa
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-27 22:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 13:46 [PATCH net] net: lan966x: fix the DB dataptr of frames from ndo_xdp_xmit Daniel Machon
2026-10-27 22:30 ` patchwork-bot+netdevbpf [this message]
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=179314020904.360855.3604879146922588076.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel.machon@microchip.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=hawk@kernel.org \
--cc=horatiu.vultur@microchip.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
/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