rte_flow_item_mark(3)

📦
version 25.11.3 · 9 versions
, in ubuntu resolute, ubuntu stonking

💖 NAME 💖

rte_flow_item_mark — bestie, it's literally the flow item that matches a mark value, periodt ✨

🦋 SYNOPSIS 🦋

#include <rte_flow.h>

🎀 Data Fields 🎀

  • uint32_t id

🌸 Detailed Description 🌸

⚠️ Warning — EXPERIMENTAL: this structure may change without prior notice 💀 like, do not get attached, bestie, it can switch up on you at ANY moment.

RTE_FLOW_ITEM_TYPE_MARK 👑

So here's the tea ☕ — this thing matches an arbitrary integer value that was set using the MARK action in a previously matched rule. You set the mark earlier in the pipeline, and now you're matching on it. Iconic behaviour honestly.

This item can only be specified once as a match criteria, because the MARK action can only be specified once in a flow action. So don't try to be extra, the rules said one 💅

This value is arbitrary and application-defined ✨. The maximum allowed value depends on the underlying implementation — so like, check with your PMD before you go feral with big numbers 🙈

Depending on the underlying implementation, the MARK item may be supported on the physical device, with virtual groups in the PMD, or not at all. It's giving "it depends" 😭 vibe check your hardware first, no cap.

Definition at line 1745 of file rte_flow.h.

🫶 Field Documentation 🫶

💜 uint32_t id

Integer value to match against. Lowkey the whole point of the struct 🍓

Definition at line 1746 of file rte_flow.h.

🌈 Author 🌈

Generated automatically by Doxygen for DPDK from the source code. Not a human, not a bestie, just a doc generator doing its little thing 🧚

And that's the whole page, mwah 💋 — this was rte_flow_item_mark(3) from DPDK, Version 25.11.3, brought to you by the DPDK crew. Slay, stay experimental, and go match some marks responsibly 👑✨

📦 where this page comes from