From: Stephen Hemminger <stephen@networkplumber.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: Alasdair McWilliam <alasdair@mcwilliam.dev>,
netdev@vger.kernel.org, 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>
Subject: Re: [PATCH] rtnetlink: add needed_{head,tail}room attributes
Date: Mon, 15 Sep 2025 10:20:05 -0700 [thread overview]
Message-ID: <20250915102005.2ddf29d7@hermes.local> (raw)
In-Reply-To: <e742f9e0-671d-4058-99af-c3e38b73ec0d@iogearbox.net>
On Mon, 15 Sep 2025 18:49:55 +0200
Daniel Borkmann <daniel@iogearbox.net> wrote:
> Hi Alasdair,
>
> On 9/15/25 6:32 PM, Alasdair McWilliam wrote:
> > Various network interface types make use of needed_{head,tail}room values
> > to efficiently reserve buffer space for additional encapsulation headers,
> > such as VXLAN, Geneve, IPSec, etc. However, it is not currently possible
> > to query these values in a generic way.
> >
> > Introduce ability to query the needed_{head,tail}room values of a network
> > device via rtnetlink, such that applications that may wish to use these
> > values can do so.
> >
> > Signed-off-by: Alasdair McWilliam <alasdair@mcwilliam.dev>
Why is this info needed in user space?
How would an application use this?
Seems like a hardware specific optimization that should be hidden in driver.
next prev parent reply other threads:[~2025-09-15 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 16:32 [PATCH] rtnetlink: add needed_{head,tail}room attributes Alasdair McWilliam
2025-09-15 16:49 ` Daniel Borkmann
2025-09-15 17:20 ` Stephen Hemminger [this message]
2025-09-15 18:30 ` Daniel Borkmann
2025-09-16 10:56 ` Alasdair McWilliam
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=20250915102005.2ddf29d7@hermes.local \
--to=stephen@networkplumber.org \
--cc=alasdair@mcwilliam.dev \
--cc=andrew+netdev@lunn.ch \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.