From: Jakub Kicinski <kuba@kernel.org>
To: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Cc: Stanislav Fomichev <stfomichev@gmail.com>,
<netdev@vger.kernel.org>, <bpf@vger.kernel.org>,
<magnus.karlsson@intel.com>, <pabeni@redhat.com>,
<horms@kernel.org>
Subject: Re: [PATCH net-next] xsk: use __xsk_rcv_zc_safe for ZC multi-buffer Rx processing
Date: Sat, 14 Mar 2026 07:46:44 -0700 [thread overview]
Message-ID: <20260314074644.027eeb3f@kernel.org> (raw)
In-Reply-To: <abPrzvYABPo7iAzq@boxer>
On Fri, 13 Mar 2026 11:49:50 +0100 Maciej Fijalkowski wrote:
> On Fri, Mar 13, 2026 at 10:31:09AM +0100, Maciej Fijalkowski wrote:
> > On Thu, Mar 12, 2026 at 05:33:48PM -0700, Jakub Kicinski wrote:
> > > The pre-req is in both trees now. Please repost?
> >
> > Will do.
>
> Argh, seems like it's not there. Maybe you meant Nikhil Rao's fixes, but
> the pre-req for this patch [0] has been applied to bpf-next, I do not see
> it on neither net-next nor net tree.
>
> On bpf-next I see this as f620af11c27b ("xsk: avoid double checking against rx
> queue being full").
>
> [0] : https://lore.kernel.org/bpf/20260218150000.301176-1-maciej.fijalkowski@intel.com/
I see, repost for bpf-next then?
next prev parent reply other threads:[~2026-03-14 14:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 13:30 [PATCH net-next] xsk: use __xsk_rcv_zc_safe for ZC multi-buffer Rx processing Maciej Fijalkowski
2026-03-10 18:22 ` kernel test robot
2026-03-10 21:59 ` Stanislav Fomichev
2026-03-13 0:33 ` Jakub Kicinski
2026-03-13 9:31 ` Maciej Fijalkowski
2026-03-13 10:49 ` Maciej Fijalkowski
2026-03-14 14:46 ` Jakub Kicinski [this message]
2026-03-10 22:10 ` kernel test robot
2026-03-11 0:36 ` Jason Xing
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=20260314074644.027eeb3f@kernel.org \
--to=kuba@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=horms@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.