DEFINITION(3)

📦 version 26.03, in nixos 26.05, nixpkgs unstable

💅 NAME 💅

rte_flow_action_nvgre_encap — okay bestie, this is the page for the NVGRE tunnel end-point encapsulation data definition, straight from the Library Functions Manual vibe. It’s giving very specific struct energy, and we’re gonna get into all of it 💖.

✨ SYNOPSIS ✨

#include <rte_flow.h>

🌸 Data Fields 🌸

  • struct rte_flow_item * definition — the field itself, no cap.

🦋 DETAILED DESCRIPTION 🦋

Warning — EXPERIMENTAL: this structure may change without prior notice. Not me telling you to be careful, but like… be careful 💀.

RTE_FLOW_ACTION_TYPE_NVGRE_ENCAP

NVGRE tunnel end-point encapsulation data definition. That’s the whole main character energy of this struct.

The tunnel definition is provided through the flow item pattern, and the provided pattern must conform with RFC7637. The flow definition must be provided in order from the RTE_FLOW_ITEM_TYPE_ETH definition up the end item, which is specified by RTE_FLOW_ITEM_TYPE_END.

The mask field allows the user to specify which fields in the flow item definitions can be ignored and which have valid data and can be used verbatim. Lowkey important, highkey useful 🫶.

Note: the last field is not used in the definition of a tunnel and can be ignored.

Valid flow definitions for RTE_FLOW_ACTION_TYPE_NVGRE_ENCAP include:

  • ETH / IPV4 / NVGRE / END
  • ETH / VLAN / IPV6 / NVGRE / END

Definition at line 3733 of file rte_flow.h. Periodt 📌.

🎀 FIELD DOCUMENTATION 🎀

struct rte_flow_item* definition

Encapsulating nvgre tunnel definition (terminated by the END pattern item).

Definition at line 3738 of file rte_flow.h. Slay, tiny but mighty ✨.

👑 AUTHOR 👑

Generated automatically by Doxygen for DPDK from the source code.

Okay bestie, that’s the whole page. It’s rte_flow_a...nvgre_encap(3) from the Library Functions Manual, DPDK version 26.03.0 — you made it to the end, and that’s iconic 💖🌈.

📦 where this page comes from