diff options
| author | Timo Völker <timo.voelker@fh-muenster.de> | 2026-01-30 10:54:33 +0000 |
|---|---|---|
| committer | Michael Tuexen <tuexen@FreeBSD.org> | 2026-01-30 10:54:33 +0000 |
| commit | 574d46b25ab6f42ad97017bb8b72520e9539e36f (patch) | |
| tree | e9dbadb05804771db9936d192ebfe5a604a8ba6c /contrib/llvm-project/llvm/lib/Target/WebAssembly/ssh:/anongit@git.FreeBSD.org/(public-mirror) | |
| parent | 33596d92555e5b1632fca14eb9af295e4b8f751c (diff) | |
Add capability VLAN_HWTAGGING to the epair interface and enable it by
default.
When sending a packet over a VLAN interface that uses an epair
interface, the flag M_VLANTAG and the ether_vtag (which contains the
VLAN ID and/or PCP) are set in the mbuf to inform the hardware that
the VLAN header has to be added. The sending epair end does not need
to actually add a VLAN header. It can just pass the mbuf with this
setting to the other epair end, which receives the packet. The
receiving epair end can just pass the mbuf with this setting to the
upper layer. Due to this setting, the upper layer believes that there
was a VLAN header that has been removed by the interface.
If the packet later leaves the host, the outgoing physical interface
can add the VLAN header in hardware if it supports VLAN_HWTAGGING.
If not, the implementation of Ethernet or bridge adds the VLAN header
in software.
Reviewed by: zlei, tuexen
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D52465
Diffstat (limited to 'contrib/llvm-project/llvm/lib/Target/WebAssembly/ssh:/anongit@git.FreeBSD.org/(public-mirror)')
0 files changed, 0 insertions, 0 deletions
