rte_flow_action_port_id(3)

✨ NAME ✨

rte_flow_action_port_id β€” it's a DPDK flow action struct, bestie, and it lives in the Library Functions Manual (section 3, aka the "these are C library functions" section, iykyk)


πŸŽ€ SYNOPSIS πŸŽ€

#include <rte_flow.h>

πŸ’« Data Fields πŸ’«

  • uint32_t original:1
  • uint32_t reserved:31
  • uint32_t id

πŸ¦‹ Detailed Description πŸ¦‹

Deprecated. πŸ’€ Yeah. She's old. She's been through things. Use the things below instead, okay?

See also πŸ‘€

  • RTE_FLOW_ACTION_TYPE_PORT_REPRESENTOR
  • RTE_FLOW_ACTION_TYPE_REPRESENTED_PORT
  • RTE_FLOW_ACTION_TYPE_PORT_ID

Okay so what does it do? It directs matching traffic to a given DPDK port ID. That's the whole vibe. Traffic matches your flow rule β†’ boom, it gets yeeted to the port ID you picked. Slay. ✨

See also 🫢

  • RTE_FLOW_ITEM_TYPE_PORT_ID

Definition at line 3552 of file rte_flow.h.


🌈 Field Documentation 🌈

⭐ uint32_t original

Use original DPDK port ID if possible. Like, if possible, bestie β€” that's the condition, don't come for me. πŸ™ˆ

Definition at line 3553 of file rte_flow.h.

πŸ’œ uint32_t reserved

Reserved, must be zero. Not "should be" β€” must. Don't be the girl who puts a 1 here. πŸ«₯

Definition at line 3554 of file rte_flow.h.

πŸ“ uint32_t id

DPDK port ID. That's it, that's the field. Short and iconic. πŸ‘‘

Definition at line 3555 of file rte_flow.h.


🌸 Author 🌸

Generated automatically by Doxygen for DPDK from the source code. So no, a human did not handcraft this prose β€” the robot did, and honestly? She ate. πŸ’…


and that's the whole page, bestie!! πŸ¦‹ This little number came to you courtesy of DPDK, Version 25.11.3, and yes, the manual page is rte_flow_action_port_id(3) β€” section 3, library functions, in case you were wondering where to find her again. mwah πŸ’– πŸŽ€ ✨

πŸ“¦ where this page comes from