rte_flow_a...plate_attr(3)

πŸ“¦ version 26.03, in nixos 26.05, nixpkgs unstable

πŸ’… NAME

rte_flow_actions_template_attr β€” ok so bestie, this is a struct from rte_flow.h (the Library Functions Manual one, iykyk) and it holds the flow actions template attributes. That's it, that's the vibe.


✨ SYNOPSIS ✨

#include <rte_flow.h>

Data Fields β€” literally just three lil bitfields, one bit each:

uint32_t ingress:1
uint32_t egress:1
uint32_t transfer:1

🌸 DESCRIPTION 🌸

⚠️ Warning β€” EXPERIMENTAL: this API may change without prior notice. So like… don't get too attached, bestie. It could get a glow-up at any moment and your code would simply have to deal. πŸ’€

This struct = flow actions template attributes. That's the whole thing. It's giving "small but mighty".

The definition lives at line 5784 of the file rte_flow.h. Go look, she's right there. πŸŽ€


πŸ¦‹ FIELD DOCUMENTATION πŸ¦‹

uint32_t ingress

The flow direction for the actions template. And listen β€” at least one direction must be specified, no cap. This bit means the action is valid for rules applied to ingress traffic.

Definition at line 5790 of rte_flow.h.

uint32_t egress

This bit means the action is valid for rules applied to egress traffic.

Definition at line 5792 of rte_flow.h.

uint32_t transfer

And this bit means the action is valid for rules applied to transfer traffic.

Definition at line 5794 of rte_flow.h.


πŸ‘‘ AUTHOR

Generated automatically by Doxygen for DPDK from the source code. Not a human, just a very diligent little robot. πŸ€–βœ¨


okay that's the whole page, mwah πŸ’– This absolute icon of a manpage came to you courtesy of DPDK, Version 26.03.0 β€” go forth and set your direction bits, bestie, and remember: at least one. 🫢🌈

πŸ“¦ where this page comes from