rte_eth_fdir_input(3)

🌸 NAME 🌸

rte_eth_fdir_input β€” bestie, this is the struct that holds all the input you hand over for a flow director filter entry. it's giving "here's what I want to match on" πŸ’…


✨ SYNOPSIS ✨

#include <rte_eth_ctrl.h>

πŸŽ€ Data Fields

  • union rte_eth_fdir_flow flow
  • struct rte_eth_fdir_flow_ext flow_ext

πŸ’– Detailed Description πŸ’–

okay so, lowkey the whole point of this thing: it's a structure used to define the input for a flow director filter entry. that's it, that's the job. main character of the "what am I filtering on" moment πŸ¦‹

Definition at line 296 of file rte_eth_ctrl.h.

πŸ‘‘ Field Documentation πŸ‘‘

🌈 union rte_eth_fdir_flow flow

the flow fields to match, bestie β€” and the way that which fields even matter here is dependent on flow_type, so don't come for me if it looks different per case, that's literally by design fr fr ✨

Definition at line 298 of file rte_eth_ctrl.h.

πŸ¦‹ struct rte_eth_fdir_flow_ext flow_ext

the additional fields to match β€” the extra lil bonus round after the flow fields, no cap πŸ’–

Definition at line 300 of file rte_eth_ctrl.h.

🧚 Author 🧚

generated automatically by Doxygen for DPDK from the source code. so like… not a human, it's the robot doing its thing and honestly it ate πŸ€–βœ¨


and that's the whole page, bestie!! this was from the DPDK manual, version 25.11.3, page rte_eth_fdir_input(3) β€” go match some flows, slay, periodt πŸ’…πŸŒˆ

πŸ“¦ where this page comes from