rte_flow_item_tcp(3)

πŸ’– NAME πŸ’–

rte_flow_item_tcp β€” bestie, this is the flow-item glow-up for TCP headers, and she's serving 🐝✨

πŸ¦‹ SYNOPSIS πŸ¦‹

#include <rte_flow.h>

🌸 Data Fields 🌸

struct rte_tcp_hdr hdr

πŸ‘‘ DESCRIPTION πŸ‘‘

RTE_FLOW_ITEM_TYPE_TCP β€” okay so when you drop this item type into your flow rule, you're telling the matcher "we're looking at a TCP header, babes." πŸ’…

It matches a TCP header. That's the whole vibe. It's giving "I know exactly what protocol I'm on and I'm not being subtle about it." πŸŽ€

Little receipt for the source-girlies: this is defined at line 1069 of file rte_flow.h. ✨

🧚 FIELD DOCUMENTATION 🧚

πŸ’œ struct rte_tcp_hdr hdr

That's the TCP header definition itself, living rent-free inside this struct. 🫢 This is the actual header you're matching against β€” the whole TCP header situation, right there.

And another receipt, since we keep it transparent: defined at line 1070 of file rte_flow.h. πŸ“–

🌈 AUTHOR 🌈

Not a human, not a bestie β€” this was generated automatically by Doxygen for DPDK, straight from the source code. The bots ate, fr fr. πŸ€–πŸ’–


And that's the whole page, bestie β€” DPDK, Version 25.11.3, manual page rte_flow_item_tcp(3). Slay, stay safe, and may your headers always match. β­πŸ§šβ€β™€οΈβœ¨

πŸ“¦ where this page comes from