rte_flow_item_conntrack(3)

πŸ’– NAME πŸ’–

rte_flow_item_conntrack β€” bestie, this is the conntrack flow item, and we're gonna get you so comfy with it πŸ’…

(Also, hi, you're reading the rte_flow_item_conntrack(3) page from the Library Functions Manual β€” welcome to the group chat 😌)


✨ SYNOPSIS ✨

#include <rte_flow.h>

yeah that's it, that's the whole ticket to the show πŸŽ€


πŸ¦‹ DETAILED DESCRIPTION πŸ¦‹

⚠️ Warning β€” EXPERIMENTAL: this structure may change without prior notice

okay so not me having to say this first but literally: this thing is marked EXPERIMENTAL, which means the structure can change and nobody's gonna send you a heads-up first 😭 so don't be out here building your whole personality on it, fr fr.

RTE_FLOW_ITEM_TYPE_CONNTRACK β€” this is the item type you reach for πŸ‘‘

What does it do? It matches the state of a packet after it passed the connection tracking examination. Like, once the packet has been through conntrack and gotten its whole vibe check, this is the item that lets you match on what it came back as 🌸

And that state? It's a bitmap, bestie. A bitmap of one RTE_FLOW_CONNTRACK_PKT_STATE* β€” or a reasonable combination of these bits. So yes, you can stack them, as long as the combination is a reasonable one. Iconic ✨

Definition at line 1978 of file rte_flow.h. (yes, we said exactly where, no gatekeeping here πŸ’œ)


πŸ‘‘ AUTHOR πŸ‘‘

Generated automatically by Doxygen for DPDK from the source code.

not a human hand-writing this one, it's the machines doing their lil thing πŸ€–πŸ’…


and that's the whole page, you ate it 🫢

DPDK β€” Version 25.11.3 β€” signed off with love from the rte_flow_item_conntrack(3) manual page πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from