From: Jakub Kicinski <kuba@kernel.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Martin KaFai Lau <martin.lau@linux.dev>,
Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
bpf <bpf@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
"Karlsson, Magnus" <magnus.karlsson@intel.com>,
Stanislav Fomichev <stfomichev@gmail.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [PATCH v2 bpf-next] xsk: use __xsk_rcv_zc_safe for ZC multi-buffer Rx processing
Date: Tue, 17 Mar 2026 18:29:20 -0700 [thread overview]
Message-ID: <20260317182920.3f4fd8eb@kernel.org> (raw)
In-Reply-To: <CAADnVQLZOUMGxNDwxhRzfx4finsF3aua31cggKpgTA6h0pjgAA@mail.gmail.com>
On Tue, 17 Mar 2026 17:57:32 -0700 Alexei Starovoitov wrote:
> > > Do you guys need it in net-next in this merge window ?
> > >
> > > We have nothing in bpf-next/net so far, so should be fine
> > > to take this patch into net-next directly?
> >
> > Somehow __xsk_rcv_zc_safe() landed in bpf-next/master f620af11c27b8ec9
> > So I think we have limited number of possible moves now :)
>
> I wasn't paying attention. We can revert it in bpf-next and reapply
> in net-next and probably route all future xsk patches to net/net-next ?
> since it doesn't have much to do with bpf anymore.
Maybe we should defer until the merge window and let it sit in Maciej's
local tree for now. It's a tiny optimization, Maciej can resend in the
next cycle.
next prev parent reply other threads:[~2026-03-18 1:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 14:05 [PATCH v2 bpf-next] xsk: use __xsk_rcv_zc_safe for ZC multi-buffer Rx processing Maciej Fijalkowski
2026-03-16 15:40 ` Stanislav Fomichev
2026-03-17 0:12 ` Jakub Kicinski
2026-03-17 15:09 ` Alexei Starovoitov
2026-03-17 22:20 ` Jakub Kicinski
2026-03-18 0:57 ` Alexei Starovoitov
2026-03-18 1:29 ` Jakub Kicinski [this message]
2026-03-18 1:43 ` Alexei Starovoitov
2026-03-18 1:52 ` Jakub Kicinski
2026-03-17 1:21 ` Jason Xing
2026-03-18 2:10 ` patchwork-bot+netdevbpf
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=20260317182920.3f4fd8eb@kernel.org \
--to=kuba@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=horms@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stfomichev@gmail.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