From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: <bpf@vger.kernel.org>, <ast@kernel.org>, <daniel@iogearbox.net>,
<hawk@kernel.org>, <ilias.apalodimas@linaro.org>,
<toke@redhat.com>, <lorenzo@kernel.org>, <netdev@vger.kernel.org>,
<magnus.karlsson@intel.com>, <andrii@kernel.org>,
<stfomichev@gmail.com>, <aleksander.lobakin@intel.com>
Subject: Re: [PATCH bpf 2/2] veth: update mem type in xdp_buff
Date: Wed, 8 Oct 2025 11:22:26 +0200 [thread overview]
Message-ID: <aOYtUmUiplUpj2Pj@boxer> (raw)
In-Reply-To: <20251007181153.5bfa78f8@kernel.org>
On Tue, Oct 07, 2025 at 06:11:53PM -0700, Jakub Kicinski wrote:
> On Tue, 7 Oct 2025 16:59:21 +0200 Maciej Fijalkowski wrote:
> > > My thinking was that we should try to bake the rxq into "conversion"
> > > APIs, draft diff below, very much unfinished and I'm probably missing
> > > some cases but hopefully gets the point across:
> >
> > That is not related IMHO. The bugs being fixed have existing rxqs. It's
> > just the mem type that needs to be correctly set per packet.
> >
> > Plus we do *not* convert frame to buff here which was your initial (on
> > point) comment WRT onstack rxqs. Traffic comes as skbs from peer's
> > ndo_start_xmit(). What you're referring to is when source is xdp_frame (in
> > veth case this is when ndo_xdp_xmit or XDP_TX is used).
>
> I guess we're slipping into a philosophical discussion but I'd say
> that the problem is that rxq stores part of what is de facto xdp buff
> state. It is evacuated into the xdp frame when frame is constructed,
> as packet is detached from driver context. We need to reconstitute it
> when we convert frame (skb, or anything else) back info an xdp buff.
So let us have mem type per xdp_buff then. Feels clunky anyways to change
it on whole rxq on xdp_buff basis. Maybe then everyone will be happy?
>
> xdp_convert_buff_to_frame() and xdp_convert_frame_to_buff() should be
> a mirror image of each other, to put it more concisely.
>
> > However the problem pointed out by AI (!) is something we should fix as
> > for XDP_{TX,REDIRECT} xdp_rxq_info is overwritten and mem type update is
> > lost.
>
> > > +/* Initialize an xdp_buff from an skb.
> > > + *
> > > + * Note: if skb has frags skb_cow_data_for_xdp() must be called first,
> > > + * or caller must otherwise guarantee that the frags come from a page pool
> > > + */
> > > +static inline
> > > +void xdp_convert_skb_to_buff(const struct xdp_frame *frame,
> > > + struct xdp_buff *xdp, struct xdp_rxq_info *rxq)
> >
> > I would expect to get skb as an input here
>
> Joł. Don't nit pick my draft diff :D It's not meant as a working patch.
Polish sneaked in so this got really under your skin :D
>
next prev parent reply other threads:[~2025-10-08 9:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 14:02 [PATCH bpf 0/2] xdp: fix page_pool leaks Maciej Fijalkowski
2025-10-03 14:02 ` [PATCH bpf 1/2] xdp: update xdp_rxq_info's mem type in XDP generic hook Maciej Fijalkowski
2025-10-03 17:29 ` Alexei Starovoitov
2025-10-07 19:39 ` Maciej Fijalkowski
2025-10-07 20:18 ` Alexei Starovoitov
2025-10-03 14:02 ` [PATCH bpf 2/2] veth: update mem type in xdp_buff Maciej Fijalkowski
2025-10-03 23:10 ` Jakub Kicinski
2025-10-07 14:59 ` Maciej Fijalkowski
2025-10-08 1:11 ` Jakub Kicinski
2025-10-08 9:22 ` Maciej Fijalkowski [this message]
2025-10-08 10:37 ` Maciej Fijalkowski
2025-10-13 23:24 ` Jakub Kicinski
2025-10-14 16:53 ` Toke Høiland-Jørgensen
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=aOYtUmUiplUpj2Pj@boxer \
--to=maciej.fijalkowski@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=kuba@kernel.org \
--cc=lorenzo@kernel.org \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=stfomichev@gmail.com \
--cc=toke@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).