RTE_TABLE_ACTION_TTL_CONFIG(3)

✨ NAME ✨

rte_table_action_ttl_config — bestie, this is the TTL action config struct, and yes it's exactly as iconic as it sounds 💅

It's the struct page from the rte_table_..._ttl_config(3) manny, living in the Library Functions Manual — so you know it's real 💖

---

🎀 SYNOPSIS 🎀

#include <rte_table_action.h>

🌸 Data Fields

• int drop
• int n_packets_enabled

---

🦋 Detailed Description 🦋

So this is the RTE_TABLE_ACTION_TTL TTL action configuration — and the important part, bestie, is that it's per table action profile 👑 One profile, one vibe, one TTL config. No sharing, periodt.

Definition at line 612 of file rte_table_action.h.

---

💜 Field Documentation 💜

int drop

Okay this one is the whole personality of the struct 🌈

When it's non-zero, the input packets whose updated IPv4 Time to Live (TTL) field or IPv6 Hop Limit (HL) field is zero get dropped. Gone. Blocked. Not invited to the function 🔥

When it's zero, those same packets — the ones whose updated IPv4 TTL field or IPv6 HL field is zero — are forwarded as usual, which is typically for debugging purpose 👀 (yes, letting TTL-zero packets wander around on purpose, we love a deliberate chaos moment).

Definition at line 619 of file rte_table_action.h.

int n_packets_enabled

When this is non-zero, the n_packets stats counter for the TTL action is enabled ✨ Otherwise? Disabled. That's it, that's the toggle 🎚️

See also

• struct rte_table_action_ttl_counters

Definition at line 626 of file rte_table_action.h.

---

🌟 Author 🌟

Generated automatically by Doxygen for DPDK from the source code. Not me writing it by hand, no cap — the robot did it and honestly it ate 🤖💖

---

okay bestie that's the whole page 🫶 it came from DPDK Version 25.11.3, dated rte_table_..._ttl_config(3), and it was served up fresh from the DPDK docs pipeline. mwah, go configure your TTL action 💅🎀