From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Chengen Du <chengen.du@canonical.com>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, alexandre.ferrieux@orange.com
Subject: Re: [PATCH] af_packet: Handle outgoing VLAN packets without hardware offloading
Date: Sat, 25 May 2024 11:51:34 -0400 [thread overview]
Message-ID: <66520906120ae_215a8029466@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <CAPza5qc+m6aK0hOn8m1OxnmNVibJQn-VFXBAnjrca+UrcmEW4g@mail.gmail.com>
> Firstly, I will submit a patch to add a new bit in the status to
> indicate the presence of VLAN information in the payload and modify
> the header's entry accordingly.
> A new member will be added to the sockaddr_ll struct to represent the
> VLAN-encapsulated protocol, thus avoiding direct modification of the
> sll_protocol.
See my earlier comments to your v1 patch. It's a minor respin. Please
don't add new members.
> Following this patch, I will work on enabling the link layer header
> via a socket option.
Let's focus on the VLAN for now.
Any expansion of the ABI requires a very clear path to use. I'd like
to see the pcap and tcpdump (or wireshark) changes that use it.
First, we need to even understand better why anything is using
SOCK_DGRAM when access to L2.5 headers is important, and whether the
process can convert to using SOCK_RAW instead.
next prev parent reply other threads:[~2024-05-25 15:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 7:03 [PATCH] af_packet: Handle outgoing VLAN packets without hardware offloading Chengen Du
2024-05-20 18:35 ` Willem de Bruijn
2024-05-21 3:31 ` Chengen Du
2024-05-21 8:35 ` Paolo Abeni
2024-05-21 13:28 ` Willem de Bruijn
2024-05-22 14:27 ` Chengen Du
2024-05-22 18:39 ` Willem de Bruijn
2024-05-22 19:54 ` alexandre.ferrieux
2024-05-23 14:17 ` Chengen Du
2024-05-23 14:52 ` Willem de Bruijn
2024-05-23 14:56 ` Willem de Bruijn
2024-05-24 14:04 ` Chengen Du
2024-05-25 15:51 ` Willem de Bruijn [this message]
2024-05-25 20:55 ` alexandre.ferrieux
2024-05-26 15:25 ` Willem de Bruijn
2024-05-27 0:18 ` alexandre.ferrieux
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=66520906120ae_215a8029466@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@gmail.com \
--cc=alexandre.ferrieux@orange.com \
--cc=chengen.du@canonical.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox