RTE_FLOW_ACTION_SET_META(3)

πŸ’– rte_flow_action_set_meta πŸ’–

okay bestie, welcome to the rte_flow_action_set_meta(3) page β€” yes it's from the Library Functions Manual, and yes it's literally just vibes about setting metadata on packets. buckle up πŸŽ€


✨ NAME ✨

rte_flow_action_set_meta β€” that's the whole name, that's the girl πŸ’…


🌸 SYNOPSIS 🌸

#include <rte_flow.h>

that's it. one include. slay.


πŸ¦‹ Detailed Description πŸ¦‹

⚠️ Warning β€” EXPERIMENTAL: this structure may change without prior notice 😭 so like, don't get too attached, she's still figuring herself out.

πŸ‘‘ RTE_FLOW_ACTION_TYPE_SET_META

so this is the action type that sets metadata. periodt.

here's the tea on how it actually works πŸ«–:

  • metadata that was set by the mbuf metadata dynamic field with the RTE_MBUF_DYNFLAG_TX_METADATA flag on egress gets overridden by this action. like, your value? gone. replaced. rip to that old metadata but this one's different πŸ’€
  • on ingress, the metadata gets carried by the mbuf metadata dynamic field with the RTE_MBUF_DYNFLAG_RX_METADATA flag β€” if it's set, obviously. conditional queen ✨
  • oh and that dynamic mbuf field? it has to be registered in advance by rte_flow_dynf_metadata_register(). no registration, no metadata. it's giving "you gotta RSVP first" πŸŽ€

Altering partial bits is supported with a mask β€” so you can touch just some of the bits, main character energy. but for bits that have never been set, you're gonna see an unpredictable value depending on the driver implementation. so like… that's undefined-ish behavior territory, don't be surprised bestie πŸ™ˆ

and for loopback/hairpin packets? metadata set on Rx/Tx may or may not be propagated to the other path depending on HW capability. so genuinely, it depends on your hardware. no cap. hardware said "we'll see" πŸ’…


🌈 RTE_FLOW_ITEM_TYPE_META 🌈

RTE_FLOW_ITEM_TYPE_META matches metadata. that's it, that's the item. complementary queen to the action. they're a matched set fr fr 🫢


⭐ Definition ⭐

Definition at line 3915 of file rte_flow.h. yes we're citing our sources, academic baddie behavior πŸ“šβœ¨


πŸ’œ Author πŸ’œ

Generated automatically by Doxygen for DPDK from the source code. so like, nobody wrote this, the robot did. iconic honestly πŸ€–βœ¨


and that's the whole page bestie!! hope you understood, ily, go set some metadata responsibly πŸ’–

this was DPDK Version 25.11.3, page rte_flow_action_set_meta(3) β€” see you in the next manpage, mwah πŸ˜˜πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from