From: Jesper Dangaard Brouer <hawk@kernel.org>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Stanislav Fomichev <stfomichev@gmail.com>,
Jon Kohler <jon@nutanix.com>
Cc: 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, linux-kernel@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 18:35:47 +0200 [thread overview]
Message-ID: <c8ad3f65-f70e-4c6e-9231-0ae709e87bfe@kernel.org> (raw)
In-Reply-To: <681b603ac8473_1e4406294a6@willemb.c.googlers.com.notmuch>
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.
>>> - xdp_headroom: Similar to skb_headroom
>>> - xdp_metadata_len: Similar to skb_metadata_len
>>>
I like naming of these.
>>> Integrate these helpers into tap, tun, and XDP implementation to start.
>>>
>>> No functional changes introduced.
>>>
>>> Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
>>> Signed-off-by: Jon Kohler <jon@nutanix.com>
>>> ---
>>> v2->v3: Integrate feedback from Stanislav
>>> https://patchwork.kernel.org/project/netdevbpf/patch/20250430201120.1794658-1-jon@nutanix.com/
>>
>> Acked-by: Stanislav Fomichev <sdf@fomichev.me>
>
> Reviewed-by: Willem de Bruijn <willemb@google.com>
>
Nacked-by: Jesper Dangaard Brouer <hawk@kernel.org>
pw: cr
next prev parent reply other threads:[~2025-05-07 16:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 12:52 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 [this message]
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
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=c8ad3f65-f70e-4c6e-9231-0ae709e87bfe@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 \
/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
Powered by JetHome