rte_flow_action_vf(3)
π rte_flow_action_vf(3) π
okay bestie, welcome to the Library Functions Manual page for rte_flow_action_vf(3) β yes that's the whole name, that's the vibe, we move. sit down, grab a boba, and let's talk about redirecting packets to virtual functions π¦
β¨ NAME β¨
rte_flow_action_vf β that's it, that's the name, iconic, no notes π
πΈ SYNOPSIS πΈ
#include <rte_flow.h>
π Data Fields π
uint32_t original:1
uint32_t reserved:31
uint32_t id
like, three fields, all of them uint32_t, two of them doing bitfield things. slay β¨
π Detailed Description π
β οΈ Deprecated β οΈ β bestie I'm so serious, this one is deprecated. it's giving "we're keeping it around but look elsewhere." no cap, go check the alternatives below π
π See also
RTE_FLOW_ACTION_TYPE_PORT_REPRESENTORRTE_FLOW_ACTION_TYPE_REPRESENTED_PORTRTE_FLOW_ACTION_TYPE_VF
okay so what does it actually do? RTE_FLOW_ACTION_TYPE_VF directs matching traffic to a given virtual function of the current device. that's the whole main character job. traffic comes in, matches, and gets sent to that VF. periodt π«
and there's more β packets that get matched by a VF pattern item can be redirected back to their original VF ID instead of the one you specified. cute, right? except π« this parameter may not be available, and it is not guaranteed to work properly if:
- the VF part is matched by a prior flow rule, or
- the packets are not addressed to a VF in the first place.
so basically: sometimes it works, sometimes it doesn't, and the manpage is NOT promising you anything. read the room, check your setup, don't come crying to me π
π Definition at line 3535 of file rte_flow.h.
π§ Field Documentation π§
uint32_t original
Use original VF ID if possible.
like, if you can send it back to where it came from, do that. "if possible" is doing a LOT of heavy lifting in that sentence though, just saying π
π Definition at line 3536 of file rte_flow.h.
uint32_t reserved
Reserved, must be zero.
bestie. it says must be zero. not "should probably be zero," not "zero-ish," ZERO. it's giving strict parent energy. if you write anything else in there you're on your own, I don't make the rules π
π Definition at line 3537 of file rte_flow.h.
uint32_t id
VF ID.
the ID of the VF. short, sweet, to the point, ate and left no crumbs π
π Definition at line 3538 of file rte_flow.h.
π Author π
Generated automatically by Doxygen for DPDK from the source code.
so like, a robot wrote this, not a person. respect honestly, the robot did fine π€β¨
and that's the whole page, bestie!! this was DPDK, Version 25.11.3, manual section rte_flow_action_vf(3) β thanks for reading all the way to the bottom, you're the real main character π«Άππ·
π¦ where this page comes from
- ubuntu resolute: dpdk-doc 25.11.3-0ubuntu0.26.04.1 Β· BSD-3-Clause
- ubuntu stonking: dpdk-doc 25.11.3-1 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms