rte_flow_item_eth(3)

πŸ“¦ version 26.03, in nixos 26.05, nixpkgs unstable

πŸ’– NAME πŸ’–

Okay bestie, this is the manual page for rte_flow_item_eth(3) β€” from the Library Functions Manual, no less. It's all about the Ethernet item for RTE flow, and we're gonna get into it. πŸ’…

✨ SYNOPSIS ✨

First things first, include the flow header:

#include <rte_flow.h>

πŸŽ€ Data Fields πŸŽ€

  • uint32_t has_vlan:1
  • uint32_t reserved:31

🌈 Detailed Description 🌈

RTE_FLOW_ITEM_TYPE_ETH

This item matches an Ethernet header. Periodt.

Inside the hdr field, the sub-field ether_type is giving either EtherType or TPID β€” it depends on whether the item is followed by a VLAN item or not. If two VLAN items follow, that sub-field refers to the outer one, and the outer one contains the inner TPID in the similar header field. The innermost VLAN item contains a layer-3 EtherType. The whole thing follows the order you see on the wire, no cap.

If the field in question contains a TPID value, only tagged packets with that specified TPID will match the pattern. Alternatively, you can match any type of tagged packets using the has_vlan field instead of the EtherType/TPID field. Also, you can leave the two fields unused. If that's the case, both tagged and untagged packets will match the pattern. Slay.

Definition at line 886 of file rte_flow.h.

🌸 Field Documentation 🌸

πŸ¦‹ struct rte_ether_addr dst

Destination MAC.

Definition at line 893 of file rte_flow.h.

πŸ¦‹ struct rte_ether_addr src

Source MAC.

Definition at line 894 of file rte_flow.h.

πŸ¦‹ rte_be16_t type

EtherType or TPID.

Definition at line 895 of file rte_flow.h.

πŸ¦‹ uint32_t has_vlan

Packet header contains at least one VLAN.

Definition at line 899 of file rte_flow.h.

πŸ¦‹ uint32_t reserved

Reserved, must be zero.

Definition at line 900 of file rte_flow.h.

πŸ’œ Author πŸ’œ

Generated automatically by Doxygen for DPDK from the source code.


Source/version tea: DPDK, Version 26.03.0. Date on the footer? Not listed, bestie β€” the page keeps that mystery alive. πŸ’…βœ¨

πŸ“¦ where this page comes from