From: Matt Fleming <matt@readmodwrite.com>
To: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"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>,
"Simon Horman" <horms@kernel.org>,
"Jesper Dangaard Brouer" <hawk@kernel.org>,
"John Fastabend" <john.fastabend@gmail.com>,
"Stanislav Fomichev" <sdf@fomichev.me>,
"Lorenzo Bianconi" <lorenzo@kernel.org>,
bpf@vger.kernel.org, netdev@vger.kernel.org,
stable@vger.kernel.org, kernel-team@cloudflare.com,
"Matt Fleming" <mfleming@cloudflare.com>
Subject: Re: [PATCH bpf] veth: convert frag_list skbs before running XDP
Date: Tue, 21 Jul 2026 14:02:07 +0100 [thread overview]
Message-ID: <al9tl_YzWmPXGweT@matt-Precision-5490> (raw)
In-Reply-To: <al9Q8yPOfQIVxvp1@boxer>
On Tue, Jul 21, 2026 at 12:58:59PM +0200, Maciej Fijalkowski wrote:
>
> Hi all,
>
> I had an RFC that made veth to reuse generic XDP code path [0]. Jakub
> commented we could have a common pp cow check on both sides. My plan is to
> revive this work as this still causes page_pool issues when AF_XDP is used
> on veth.
>
> [0]: https://lore.kernel.org/bpf/20260509084858.773921-1-maciej.fijalkowski@intel.com/
That sounds great. I'd be happy to test out the next version.
Thanks,
Matt
prev parent reply other threads:[~2026-07-21 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 10:06 [PATCH bpf] veth: convert frag_list skbs before running XDP Matt Fleming
2026-07-17 9:56 ` Toke Høiland-Jørgensen
2026-07-20 10:24 ` Matt Fleming
2026-07-21 10:58 ` Maciej Fijalkowski
2026-07-21 13:02 ` Matt Fleming [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=al9tl_YzWmPXGweT@matt-Precision-5490 \
--to=matt@readmodwrite.com \
--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=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=lorenzo@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=mfleming@cloudflare.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=stable@vger.kernel.org \
--cc=toke@toke.dk \
/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).