From: Jakub Kicinski <kuba@kernel.org>
To: Jesper Dangaard Brouer <hawk@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
daniel@iogearbox.net, john.fastabend@gmail.com, sdf@fomichev.me,
michael.chan@broadcom.com, anthony.l.nguyen@intel.com,
marcin.s.wojtas@gmail.com, tariqt@nvidia.com, mbloch@nvidia.com,
jasowang@redhat.com, bpf@vger.kernel.org,
aleksander.lobakin@intel.com, pavan.chebbi@broadcom.com,
przemyslaw.kitszel@intel.com
Subject: Re: [PATCH net-next 1/2] net: xdp: pass full flags to xdp_update_skb_shared_info()
Date: Tue, 9 Sep 2025 16:24:14 -0700 [thread overview]
Message-ID: <20250909162414.0cf09278@kernel.org> (raw)
In-Reply-To: <669d9245-ac4b-4d43-aea3-cc30ac5836a4@kernel.org>
On Tue, 9 Sep 2025 15:30:00 +0200 Jesper Dangaard Brouer wrote:
> I'm fine with the name xdp_update_skb_frags_info().
> But I want to point out that the function *does* also update shinfo.
> The xdp_buff/xdp-frame have a compatible layout for shinfo, except for a
> union with sinfo->destructor_arg, which we need to clear. This is a
> transition point from XDP to SKB, which is why I think the function name
> change is appropiate.
Fair point.
My initial confusion was because I expected xdp_update_skb_shared_info()
to _only_ update shinfo.
> > Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> > ---
> > v1:
> > - rename skb_flags arg to xdp_flags
>
> Thanks for that. You kept the function name xdp_buff_get_skb_flags(),
> indicating this is "skb_flags". I don't think it matters much, so to
> avoid bikesheeting I'm just going to ACK this.
Thanks! Happy to respin with whatever names, if anyone expresses
a strong opinion. Otherwise I'll fix the typo and apply tomorrow.
Indeed the risk of bikeshedding is rather high here :)
next prev parent reply other threads:[~2025-09-09 23:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 22:15 [PATCH net-next 0/2] net: xdp: handle frags with unreadable memory Jakub Kicinski
2025-09-05 22:15 ` [PATCH net-next 1/2] net: xdp: pass full flags to xdp_update_skb_shared_info() Jakub Kicinski
2025-09-09 13:30 ` Jesper Dangaard Brouer
2025-09-09 23:24 ` Jakub Kicinski [this message]
2025-09-05 22:15 ` [PATCH net-next 2/2] net: xdp: handle frags with unreadable memory Jakub Kicinski
2025-09-05 22:55 ` [PATCH net-next 0/2] " Stanislav Fomichev
2025-09-08 12:02 ` Alexander Lobakin
2025-09-11 10: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=20250909162414.0cf09278@kernel.org \
--to=kuba@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--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=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=marcin.s.wojtas@gmail.com \
--cc=mbloch@nvidia.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=sdf@fomichev.me \
--cc=tariqt@nvidia.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.