rte_flow_p...plate_attr(3)

πŸ’– NAME πŸ’–

rte_flow_pattern_template_attr β€” bestie, this is the struct that holds all the vibes (okay, all the attributes) for a flow pattern template ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

#include <rte_flow.h>

πŸŽ€ Data Fields

  • uint32_t relaxed_matching:1
  • uint32_t ingress:1
  • uint32_t egress:1
  • uint32_t transfer:1

🌸 Detailed Description 🌸

⚠️ Warning β€” EXPERIMENTAL: this API may change without prior notice. So like… don't get too attached, she's still figuring herself out πŸ’…

Flow pattern template attributes. That's the whole vibe. Definition at line 5691 of file rte_flow.h.


πŸ”₯ Field Documentation πŸ”₯

🌈 uint32_t relaxed_matching

Relaxed matching policy, aka the "how picky are we being" setting 🧚

  • If it's 1, matching is performed only on items with the mask member set, and matching on protocol layers specified without any masks is skipped. Lowkey unbothered, highkey efficient.
  • If it's 0, matching on protocol layers specified without any masks is done as well. This is the standard behaviour of Flow API now β€” fr fr, this is the default girlie.

Definition at line 5699 of file rte_flow.h.

🫢 uint32_t ingress

Flow direction for the pattern template. At least one direction must be specified β€” no direction, no deal, periodt. This one means the pattern is valid for rules applied to ingress traffic. Come on in, the packets are lovely πŸ’–

Definition at line 5705 of file rte_flow.h.

πŸ’œ uint32_t egress

Pattern valid for rules applied to egress traffic. She's leaving, but make it iconic ✨

Definition at line 5707 of file rte_flow.h.

⭐ uint32_t transfer

Pattern valid for rules applied to transfer traffic. Transporting, but make it a whole personality 😭

Definition at line 5709 of file rte_flow.h.


πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for DPDK from the source code. Not me writing it by hand, the robots ate and left no crumbs πŸ€–πŸ’…


okay bestie, that's the whole page πŸŽ€ this was DPDK, Version 25.11.3, serving rte_flow_p...plate_attr(3) realness from a Library Functions Manual β€” mwah, go touch some packets, ily πŸ¦‹πŸ’–

πŸ“¦ where this page comes from