rte_flow_action_jump(3)

✨ NAME ✨

rte_flow_action_jump β€” okay bestie, this is the whole entire page, and yes the name is just the name, that's how these library function manual pages from the Library Functions Manual work, we don't make the rules πŸ’…


🫢 SYNOPSIS 🫢

#include <rte_flow.h>

that's it. that's the include. go off πŸŽ€


πŸ’… Detailed Description πŸ’…

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

ngl that warning is giving "don't get attached, she's not yours" energy. lowkey important: this thing is experimental, so it can shift under you with zero heads-up. no cap.

RTE_FLOW_ACTION_TYPE_JUMP πŸ‘‘

Redirects packets to a group on the current device. like, the packets are leaving and they're going to that group specifically. slay.

In a hierarchy of groups, which can be used to represent physical or logical flow tables on the device, this action allows the action to be a redirect to a group on that device. so picture a whole little group hierarchy β€” physical flow tables, logical flow tables, the whole vibe β€” and this action is your main character move: it lets the action be a redirect to a group on that device. it's giving "you're not stuck here, you're going there" ✨

Definition at line 3359 of file rte_flow.h. (yes we cite our sources, we're nothing if not academic πŸ’–)


🌸 Author 🌸

Generated automatically by Doxygen for DPDK from the source code. not me writing my own autobiography but make it a code generator 🧚


okay that's the page!! this was DPDK Version 25.11.3, and the page itself is rte_flow_action_jump(3) in that classic Library Functions Manual fit. bye bestie, redirect responsibly πŸ¦‹πŸ’œ

πŸ“¦ where this page comes from