rte_flow_item(3)

💖 NAME 💖

rte_flow_item

Bestie, you're on the rte_flow_item(3) page from the Library Functions Manual — let's go 💅

✨ SYNOPSIS ✨

#include <rte_flow.h>

🧸 Data Fields 🧸

• enum rte_flow_item_type type — item type, iykyk 🎀
• const void * spec — pointer to spec item specification structure ✨
• const void * last — defines an inclusive range (spec to last) 🌸
• const void * mask — bit-mask applied to spec and last 💅

🦋 Detailed Description 🦋

Okay so a matching pattern item definition is the whole vibe here. A pattern is formed by stacking items starting from the lowest protocol layer to match. That stacking restriction does not apply to meta items, which can have main character energy and be placed anywhere in the stack without affecting the meaning of the resulting pattern — slay, periodt ✨

Patterns are terminated by END items — iconic, necessary, no cap.

The spec field should be a valid pointer to a structure of the related item type. It may remain unspecified (NULL) in many cases to request broad (nonspecific) matching. In such cases, last and mask must also be set to NULL, fr fr 🫶

Optionally, last can point to a structure of the same type to define an inclusive range. This is mostly supported by integer and address fields, may cause errors otherwise. Fields that do not support ranges must be set to 0 or to the same value as the corresponding fields in spec 😭

Only the fields defined to nonzero values in the default masks (see rte_flow_item_{name}_mask constants) are considered relevant by default. This can be overridden by providing a mask structure of the same type with applicable bits set to one. It can also be used to partially filter out specific fields (e.g. as an alternate mean to match ranges of IP addresses) 💅

mask is a simple bit-mask applied before interpreting the contents of spec and last; highkey, this may yield unexpected results if not used carefully. For example, if for an IPv4 address field, spec provides 10.1.2.3, last provides 10.3.4.5 and mask provides 255.255.0.0, the effective range becomes 10.1.0.0 to 10.3.255.255. Not me making a mask mistake and getting a whole unexpected range 💀

Definition at line 2127 of file rte_flow.h.

🫶 Field Documentation 🫶

🌸 enum rte_flow_item_type type 🌸

Item type. Definition at line 2128 of file rte_flow.h.

✨ const void* spec ✨

Pointer to item specification structure. Definition at line 2129 of file rte_flow.h.

🎀 const void* last 🎀

Defines an inclusive range (spec to last). Definition at line 2130 of file rte_flow.h.

💅 const void* mask 💅

Bit-mask applied to spec and last. Definition at line 2131 of file rte_flow.h.

🌈 Author 🌈

Generated automatically by Doxygen for DPDK from the source code.

---

that's the whole page, bestie 💖 source/version: DPDK, Version 26.03.0; date: not listed in this footer, so no invented date 😭 — mwah 🫶✨