From: Jesper Dangaard Brouer <hawk@kernel.org>
To: Jon Kohler <jon@nutanix.com>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: Zvi Effron <zeffron@riotgames.com>,
Stanislav Fomichev <stfomichev@gmail.com>,
Jason Wang <jasowang@redhat.com>,
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>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
Simon Horman <horms@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
Jacob Keller <jacob.e.keller@intel.com>
Subject: Re: [PATCH net-next v3] xdp: Add helpers for head length, headroom, and metadata length
Date: Wed, 7 May 2025 21:04:51 +0200 [thread overview]
Message-ID: <e4cf6912-74fb-441f-ad05-82ea99d81020@kernel.org> (raw)
In-Reply-To: <B4F050C6-610F-4D04-88D7-7EF581DA7DF1@nutanix.com>
On 07/05/2025 19.47, Jon Kohler wrote:
>
>
>> On May 7, 2025, at 1:21 PM, Willem de Bruijn <willemdebruijn.kernel@gmail.com> wrote:
>>
>>
>> Jesper Dangaard Brouer wrote:
>>>
>>>
>>> On 07/05/2025 19.02, Zvi Effron wrote:
>>>> On Wed, May 7, 2025 at 9:37 AM Jesper Dangaard Brouer <hawk@kernel.org> wrote:
>>>>>
>>>>>
>>>>>
>>>>> On 07/05/2025 15.29, Willem de Bruijn wrote:
>>>>>> Stanislav Fomichev wrote:
>>>>>>> On 05/06, Jon Kohler wrote:
>>>>>>>> Introduce new XDP helpers:
>>>>>>>> - xdp_headlen: Similar to skb_headlen
>>>>>
>>>>> I really dislike xdp_headlen(). This "headlen" originates from an SKB
>>>>> implementation detail, that I don't think we should carry over into XDP
>>>>> land.
>>>>> We need to come up with something that isn't easily mis-read as the
>>>>> header-length.
>>>>
>>>> ... snip ...
>>>>
>>>>>>> + * xdp_headlen - Calculate the length of the data in an XDP buffer
>>>>
>>>> How about xdp_datalen()?
>>>
>>> Yes, I like xdp_datalen() :-)
>>
>> This is confusing in that it is the inverse of skb->data_len:
>> which is exactly the part of the data not in the skb head.
>>
>> There is value in consistent naming. I've never confused headlen
>> with header len.
>>
>> But if diverging, at least let's choose something not
>> associated with skbs with a different meaning.
>
> Brainstorming a few options:
> - xdp_head_datalen() ?
> - xdp_base_datalen() ?
> - xdp_base_headlen() ?
> - xdp_buff_datalen() ?
> - xdp_buff_headlen() ?
> - xdp_datalen() ? (ZivE, JesperB)
> - xdp_headlen() ? (WillemB, JonK, StanislavF, JacobK, DanielB)
>
What about keeping it really simple: xdp_buff_len() ?
Or even simpler: xdp_len() as the function documentation already
describe this doesn't include frags.
To Jon, you seems to be on a cleanup spree:
For SKBs netstack have this diagram documented [1]. Which also explains
the concept of a "head" buffer, which isn't a concept for XDP. I would
really like to see a diagram documenting both xdp_buff and xdp_frame
data structures via ascii art, like the one for SKBs. (Hint, this is
actually defined in the header file include/linux/skbuff.h, but
converted to RST/HTML format.)
[1] https://docs.kernel.org/networking/skbuff.html
--Jesper
next prev parent reply other threads:[~2025-05-07 19:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 12:52 [PATCH net-next v3] xdp: Add helpers for head length, headroom, and metadata length Jon Kohler
2025-05-06 17:43 ` Stanislav Fomichev
2025-05-07 13:29 ` Willem de Bruijn
2025-05-07 16:35 ` Jesper Dangaard Brouer
2025-05-07 17:02 ` Zvi Effron
2025-05-07 17:08 ` Jesper Dangaard Brouer
2025-05-07 17:21 ` Willem de Bruijn
2025-05-07 17:47 ` Jon Kohler
2025-05-07 19:04 ` Jesper Dangaard Brouer [this message]
2025-05-07 19:57 ` Jon Kohler
2025-05-07 20:58 ` Jesper Dangaard Brouer
2025-05-08 0:18 ` Jakub Kicinski
2025-05-08 3:19 ` Jon Kohler
2025-05-09 1:28 ` Jakub Kicinski
2025-05-08 3:18 ` Jon Kohler
2025-05-08 16:59 ` Jesper Dangaard Brouer
2025-05-09 1:26 ` Jakub Kicinski
2025-05-07 16:18 ` Daniel Borkmann
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=e4cf6912-74fb-441f-ad05-82ea99d81020@kernel.org \
--to=hawk@kernel.org \
--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=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=jon@nutanix.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stfomichev@gmail.com \
--cc=willemdebruijn.kernel@gmail.com \
--cc=zeffron@riotgames.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;
as well as URLs for NNTP newsgroup(s).