rte_flow_action_age(3)

💖 NAME 💖

rte_flow_action_age — bestie, this is the age action struct from the flow API, and she's here to tell you when a flow has been ghosting you 👻

---

✨ SYNOPSIS ✨

#include <rte_flow.h>

🎀 Data Fields 🎀

• uint32_t timeout:24
• uint32_t reserved:8
• void * context

---

🌸 Detailed Description 🌸

⚠️ Warning — EXPERIMENTAL: this structure may change without prior notice. Like, without prior notice bestie. Do not get attached 💀

RTE_FLOW_ACTION_TYPE_AGE

So here's the tea 🍵 — this action reports a flow as aged-out if timeout passed without any matching on the flow. Basically if nobody hits your flow for the whole timeout window, she's officially aged-out, no cap.

When a port detects new aged-out flows, the RTE_ETH_EVENT_FLOW_AGED event gets triggered. That's your lil notification bell going off 🔔

The flow context and the flow handle both get reported by either rte_flow_get_aged_flows or rte_flow_get_q_aged_flows APIs. Pick your fighter, both of them spill ✨

Definition at line 3385 of file rte_flow.h.

---

🦋 Field Documentation 🦋

uint32_t timeout

Time in seconds ⏰ — that's it, that's the field.

Definition at line 3386 of file rte_flow.h.

uint32_t reserved

Reserved — must be zero. Like, actually zero, not "eh close enough" zero. Zero zero. 🙈

Definition at line 3387 of file rte_flow.h.

void* context

The user flow context, and if it's NULL that means it's the rte_flow pointer instead. Simple as 👑

Definition at line 3389 of file rte_flow.h.

---

👑 Author 👑

Generated automatically by Doxygen for DPDK from the source code. Not a human, not a girlie, just Doxygen doing her thing 🤖✨

---

Okay bestie that's the whole page, mwah 💅 This was DPDK, Version 25.11.3, and you've been reading rte_flow_action_age(3) — go forth and let those flows age out gracefully 🦋💖