rte_flow_item_fuzzy(3)

📦
version 25.11.3 · 9 versions
, in ubuntu resolute, ubuntu stonking

💖 rte_flow_item_fuzzy 💖

okay bestie, so this one is a manual page for the rte_flow_item_fuzzy thing in DPDK — it's a library functions manual situation, and yes it's literally just about one fuzzy little struct. let's get into it 🦋

✨ NAME ✨

rte_flow_item_fuzzy — the fuzzy pattern match item, iykyk

✨ SYNOPSIS ✨

#include <rte_flow.h>

🌸 Data Fields 🌸

uint32_t thresh

✨ Detailed Description ✨

RTE_FLOW_ITEM_TYPE_FUZZY 💅

So it's a fuzzy pattern match, and the whole point is that it's expected to be faster than default. Lowkey the tradeoff queen of pattern matching fr fr.

This exists for devices that support a fuzzy match option. And here's the tea: usually a fuzzy match is fast, but the cost is accuracy. Like, Signature Match only matches the pattern's hash value, but it's totally possible that two different patterns end up with the same hash value. 😭 iconic behavior, honestly.

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

Now, the numbers — memorize these bestie:

  • Threshold 0 means perfect match (no fuzziness). No cap. ✨
  • Threshold 0xffffffff means fuzziest match. Maximum chaos. 💀
Definition at line 1266 of file rte_flow.h.

✨ Field Documentation ✨

🌈 uint32_t thresh 🌈

Accuracy threshold. That's it, that's the field. 🎀

Definition at line 1267 of file rte_flow.h.

✨ Author ✨

Generated automatically by Doxygen for DPDK from the source code. (not a human author, just a robot doing its little robot thing 🫶)

and that's the whole page, bestie!! this was DPDK Version 25.11.3, mwah 💋 go forth and fuzzy match responsibly, no fuzziness at 0, maximum fuzziness at 0xffffffff, slay 👑✨

📦 where this page comes from