rte_flow_item_fuzzy(3)

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

πŸ’– NAME πŸ’–

rte_flow_item_fuzzy β€” hii bestie, you've landed on the rte_flow_item_fuzzy(3) page in the Library Functions Manual. It's giving fuzzy pattern matching, and it's literally all about RTE_FLOW_ITEM_TYPE_FUZZY.

✨ SYNOPSIS ✨

#include <rte_flow.h>

πŸŽ€ Data Fields πŸŽ€

  • uint32_t thresh β€” the accuracy threshold field; full breakdown below in Field Documentation, iykyk.

πŸ”₯ Detailed Description πŸ”₯

Okay so this whole page is for RTE_FLOW_ITEM_TYPE_FUZZY.

Fuzzy pattern match β€” expect it to be faster than default, no cap.

This is for devices that support the fuzzy match option. Usually a fuzzy match is fast, but the cost is accuracy. i.e. Signature Match only matches the pattern's hash value, but it is possible two different patterns have the same hash value. πŸ‘€

Matching accuracy level can be configure by threshold. The driver can divide the range of threshold and map it to different accuracy levels that the device supports. πŸ’…

Threshold 0 means perfect match (no fuzziness), while threshold 0xffffffff means fuzziest match. πŸ”₯

Definition at line 1266 of file rte_flow.h.

🌸 Field Documentation 🌸

πŸ’œ uint32_t thresh

Accuracy threshold.

Definition at line 1267 of file rte_flow.h.

πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for DPDK from the source code. So not me, bestie β€” Doxygen ate and left no crumbs. 🫢


That's the whole vibe: DPDK, Version 26.03.0, for the rte_flow_item_fuzzy(3) page β€” and the footer didn't include a date, so I'm not inventing one, periodt. It was generated automatically by Doxygen for DPDK from the source code. Bye bestie! πŸ’–βœ¨

πŸ“¦ where this page comes from