rte_flow_item_meta(3)

📦
version 25.11.3 · 9 versions
, in ubuntu resolute, ubuntu stonking

💖 NAME 💖

rte_flow_item_meta — bestie, this is the flow item that matches metadata, and honestly? it's giving underrated icon energy ✨

🦋 SYNOPSIS 🦋

#include <rte_flow.h>

🌸 DETAILED DESCRIPTION 🌸

okay so say it with me: RTE_FLOW_ITEM_TYPE_META 🎀

This is the flow item type that matches a specified metadata value. Simple. Elegant. Ate. 💅

Now let's talk about egress, because the way metadata gets set out there is a choose-your-own-adventure situation 🦋 on egress, the metadata can be set either by:

  • the mbuf dynamic metadata field, using the RTE_MBUF_DYNFLAG_TX_METADATA flag, or
  • RTE_FLOW_ACTION_TYPE_SET_META

Two paths, same destination, no cap 💫

Now flip to ingress 🧚 here's the tea: RTE_FLOW_ACTION_TYPE_SET_META sets metadata for a packet, and then that metadata gets reported back via the mbuf metadata dynamic field with the RTE_MBUF_DYNFLAG_RX_METADATA flag. She tells you everything, fr fr 💖

⚠️ super important, bestie, do not skip this: the dynamic mbuf field must be registered in advance by rte_flow_dynf_metadata_register(). No registration, no metadata. It's giving "read the instructions before you complain" 😭

also for the record, this whole thing is defined at line 1622 of file rte_flow.h 📖

👑 AUTHOR 👑

Generated automatically by Doxygen for DPDK, straight from the source code 🌈 it literally wrote itself, main character behavior tbh 💀

🫶 SEE ALSO 🫶

literally nothing else listed here, so go forth and slay on your own, iykyk 💜

and that's the whole page, bestie!! 🎀 this was DPDK Version 25.11.3, rte_flow_item_meta(3), mwah, xoxo, register your dynf metadata fields before you use them, periodt 💅✨

📦 where this page comes from