From: Jakub Kicinski <kuba@kernel•org>
To: Larysa Zaremba <larysa.zaremba@intel•com>
Cc: bpf@vger•kernel.org, "Claudiu Manoil" <claudiu.manoil@nxp•com>,
"Vladimir Oltean" <vladimir.oltean@nxp•com>,
"Wei Fang" <wei.fang@nxp•com>,
"Clark Wang" <xiaoning.wang@nxp•com>,
"Andrew Lunn" <andrew+netdev@lunn•ch>,
"David S. Miller" <davem@davemloft•net>,
"Eric Dumazet" <edumazet@google•com>,
"Paolo Abeni" <pabeni@redhat•com>,
"Tony Nguyen" <anthony.l.nguyen@intel•com>,
"Przemek Kitszel" <przemyslaw.kitszel@intel•com>,
"Alexei Starovoitov" <ast@kernel•org>,
"Daniel Borkmann" <daniel@iogearbox•net>,
"Jesper Dangaard Brouer" <hawk@kernel•org>,
"John Fastabend" <john.fastabend@gmail•com>,
"Stanislav Fomichev" <sdf@fomichev•me>,
"Andrii Nakryiko" <andrii@kernel•org>,
"Martin KaFai Lau" <martin.lau@linux•dev>,
"Eduard Zingerman" <eddyz87@gmail•com>,
"Song Liu" <song@kernel•org>,
"Yonghong Song" <yonghong.song@linux•dev>,
"KP Singh" <kpsingh@kernel•org>, "Hao Luo" <haoluo@google•com>,
"Jiri Olsa" <jolsa@kernel•org>, "Simon Horman" <horms@kernel•org>,
"Shuah Khan" <shuah@kernel•org>,
"Alexander Lobakin" <aleksander.lobakin@intel•com>,
"Maciej Fijalkowski" <maciej.fijalkowski@intel•com>,
"Bastien Curutchet (eBPF Foundation)"
<bastien.curutchet@bootlin•com>,
"Tushar Vyavahare" <tushar.vyavahare@intel•com>,
"Jason Xing" <kernelxing@tencent•com>,
"Ricardo B. Marlière" <rbm@suse•com>,
"Eelco Chaudron" <echaudro@redhat•com>,
"Lorenzo Bianconi" <lorenzo@kernel•org>,
"Toke Hoiland-Jorgensen" <toke@redhat•com>,
imx@lists•linux.dev, netdev@vger•kernel.org,
linux-kernel@vger•kernel.org, intel-wired-lan@lists•osuosl.org,
linux-kselftest@vger•kernel.org,
"Aleksandr Loktionov" <aleksandr.loktionov@intel•com>,
"Dragos Tatulea" <dtatulea@nvidia•com>
Subject: Re: [PATCH bpf v4 0/9] Address XDP frags having negative tailroom
Date: Wed, 4 Mar 2026 18:55:31 -0800 [thread overview]
Message-ID: <20260304185531.4f49fda4@kernel.org> (raw)
In-Reply-To: <20260302161723.858616-1-larysa.zaremba@intel.com>
On Mon, 2 Mar 2026 17:17:13 +0100 Larysa Zaremba wrote:
> Aside from the issue described below, tailroom calculation does not account
> for pages being split between frags, e.g. in i40e, enetc and
> AF_XDP ZC with smaller chunks. These series address the problem by
> calculating modulo (skb_frag_off() % rxq->frag_size) in order to get
> data offset within a smaller block of memory. Please note, xskxceiver
> tail grow test passes without modulo e.g. in xdpdrv mode on i40e,
> because there is not enough descriptors to get to flipped buffers.
This was re-assigned to netdev in pw, I presume by BPF maintainers.
But it doesn't apply to net. There's a conflict in ice.
Could you rebase on net and repost?
next prev parent reply other threads:[~2026-03-05 2:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 16:17 [PATCH bpf v4 0/9] Address XDP frags having negative tailroom Larysa Zaremba
2026-03-02 16:17 ` [PATCH bpf v4 1/9] xdp: use modulo operation to calculate XDP frag tailroom Larysa Zaremba
2026-03-02 16:17 ` [PATCH bpf v4 2/9] xsk: introduce helper to determine rxq->frag_size Larysa Zaremba
2026-03-02 16:17 ` [PATCH bpf v4 3/9] ice: fix rxq info registering in mbuf packets Larysa Zaremba
2026-03-02 16:17 ` [PATCH bpf v4 4/9] ice: change XDP RxQ frag_size from DMA write length to xdp.frame_sz Larysa Zaremba
2026-03-02 16:17 ` [PATCH bpf v4 5/9] i40e: fix registering XDP RxQ info Larysa Zaremba
2026-03-02 16:17 ` [PATCH bpf v4 6/9] i40e: use xdp.frame_sz as XDP RxQ info frag_size Larysa Zaremba
2026-03-02 17:32 ` bot+bpf-ci
2026-03-02 16:17 ` [PATCH bpf v4 7/9] libeth, idpf: use truesize " Larysa Zaremba
2026-03-02 16:17 ` [PATCH bpf v4 8/9] net: enetc: " Larysa Zaremba
2026-03-02 16:17 ` [PATCH bpf v4 9/9] xdp: produce a warning when calculated tailroom is negative Larysa Zaremba
2026-03-05 2:55 ` Jakub Kicinski [this message]
2026-03-05 11:48 ` [PATCH bpf v4 0/9] Address XDP frags having negative tailroom Larysa Zaremba
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=20260304185531.4f49fda4@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=aleksander.lobakin@intel$(echo .)com \
--cc=aleksandr.loktionov@intel$(echo .)com \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=andrii@kernel$(echo .)org \
--cc=anthony.l.nguyen@intel$(echo .)com \
--cc=ast@kernel$(echo .)org \
--cc=bastien.curutchet@bootlin$(echo .)com \
--cc=bpf@vger$(echo .)kernel.org \
--cc=claudiu.manoil@nxp$(echo .)com \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=dtatulea@nvidia$(echo .)com \
--cc=echaudro@redhat$(echo .)com \
--cc=eddyz87@gmail$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=haoluo@google$(echo .)com \
--cc=hawk@kernel$(echo .)org \
--cc=horms@kernel$(echo .)org \
--cc=imx@lists$(echo .)linux.dev \
--cc=intel-wired-lan@lists$(echo .)osuosl.org \
--cc=john.fastabend@gmail$(echo .)com \
--cc=jolsa@kernel$(echo .)org \
--cc=kernelxing@tencent$(echo .)com \
--cc=kpsingh@kernel$(echo .)org \
--cc=larysa.zaremba@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-kselftest@vger$(echo .)kernel.org \
--cc=lorenzo@kernel$(echo .)org \
--cc=maciej.fijalkowski@intel$(echo .)com \
--cc=martin.lau@linux$(echo .)dev \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=przemyslaw.kitszel@intel$(echo .)com \
--cc=rbm@suse$(echo .)com \
--cc=sdf@fomichev$(echo .)me \
--cc=shuah@kernel$(echo .)org \
--cc=song@kernel$(echo .)org \
--cc=toke@redhat$(echo .)com \
--cc=tushar.vyavahare@intel$(echo .)com \
--cc=vladimir.oltean@nxp$(echo .)com \
--cc=wei.fang@nxp$(echo .)com \
--cc=xiaoning.wang@nxp$(echo .)com \
--cc=yonghong.song@linux$(echo .)dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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