From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Felix Maurer <fmaurer@redhat.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Richard Cochran <richardcochran@gmail.com>,
Simon Horman <horms@kernel.org>
Subject: Re: [PATCH RFC net-next 1/2] hsr: Allow to send a specific port and with HSR header
Date: Wed, 4 Mar 2026 17:12:55 +0100 [thread overview]
Message-ID: <20260304161255.VV_7vPBw@linutronix.de> (raw)
In-Reply-To: <willemdebruijn.kernel.1d699189fce58@gmail.com>
On 2026-03-04 10:56:16 [-0500], Willem de Bruijn wrote:
> Sebastian Andrzej Siewior wrote:
> > Would it be okay if I occupy three bits in sk_buff which look unused?
>
> Have you looked into using skb_extensions?
Yes. I would have allocate memory via __skb_ext_alloc() and attach it to
the skb via __skb_ext_set(). That would on receive and while sending
(via af_packet).
Looking at the current allocations as of skb_ext_type_len, they all need
a bit of memory, the smallest is mctp_flow with just a pointer the other
are a fair amount larger. For the three bits, I was hoping to avoid it.
Sebastian
next prev parent reply other threads:[~2026-03-04 16:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 11:24 [PATCH RFC net-next 0/2] hsr: Add additional info to send/ receive skbs Sebastian Andrzej Siewior
2026-02-04 11:24 ` [PATCH RFC net-next 1/2] hsr: Allow to send a specific port and with HSR header Sebastian Andrzej Siewior
2026-02-04 17:30 ` Willem de Bruijn
2026-02-17 15:36 ` Sebastian Andrzej Siewior
2026-03-04 14:58 ` Sebastian Andrzej Siewior
2026-03-04 15:56 ` Willem de Bruijn
2026-03-04 16:12 ` Sebastian Andrzej Siewior [this message]
2026-03-04 23:48 ` Willem de Bruijn
2026-03-05 8:07 ` Sebastian Andrzej Siewior
2026-03-05 14:41 ` Jakub Kicinski
2026-03-05 15:05 ` Sebastian Andrzej Siewior
2026-02-04 11:24 ` [PATCH RFC net-next 2/2] af_packet: Add port specific handling for HSR Sebastian Andrzej Siewior
2026-02-04 17:36 ` Willem de Bruijn
2026-02-17 15:51 ` Sebastian Andrzej Siewior
2026-02-16 16:10 ` [PATCH RFC net-next 0/2] hsr: Add additional info to send/ receive skbs Felix Maurer
2026-02-16 16:19 ` Sebastian Andrzej Siewior
2026-02-16 16:25 ` Andrew Lunn
2026-02-17 16:14 ` Sebastian Andrzej Siewior
2026-02-17 16:10 ` Sebastian Andrzej Siewior
2026-02-18 19:28 ` Felix Maurer
2026-02-18 21:53 ` Willem de Bruijn
2026-02-24 11:48 ` Sebastian Andrzej Siewior
2026-02-24 11:24 ` Sebastian Andrzej Siewior
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=20260304161255.VV_7vPBw@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fmaurer@redhat.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@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