rte_regexdev_match(3)

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

🌸 NAME 🌸

rte_regexdev_match β€” bestie, this is the page for it, straight out of the Library Functions Manual πŸ’…


✨ SYNOPSIS ✨

#include <rte_regexdev.h>

πŸ¦‹ DETAILED DESCRIPTION πŸ¦‹

Okay so picture this: rte_regexdev_match is the generic structure that holds your RegEx match attributes. That's the whole vibe β€” it's the little container where a match's deets live. πŸŽ€

See also: struct rte_regex_ops::matches β€” the way these two are linked? iconic. πŸ‘‘

Definition at line 1245 of file rte_regexdev.h. Noted. πŸ“

🌈 FIELD DOCUMENTATION 🌈

πŸ’– uint32_t rule_id

The rule identifier β€” like, which rule did your pattern actually match? That one. ✨

See also: struct rte_regexdev_rule::rule_id

Definition at line 1249 of file rte_regexdev.h.

🩷 uint32_t group_id

The group identifier of the rule that your pattern matched. Group chat, but make it regex. πŸ’¬

See also: struct rte_regexdev_rule::group_id

Definition at line 1253 of file rte_regexdev.h.

⭐ uint16_t start_offset

Starting Byte Position for the matched rule. Where the slay begins, literally. πŸ“

Definition at line 1257 of file rte_regexdev.h.

πŸ“ uint16_t len

Length of the match, in bytes. Gotta know how much match you're working with. πŸ“

Definition at line 1260 of file rte_regexdev.h.

🧚 uint16_t end_offset

The end offset of the match β€” but heads up, this one only applies in case the MATCH_AS_END configuration is enabled. Read that again bestie, it's conditional! πŸ™ˆ

See also: RTE_REGEXDEV_CFG_MATCH_AS_END

Definition at line 1262 of file rte_regexdev.h.

πŸ‘‘ AUTHOR πŸ‘‘

Generated automatically by Doxygen for DPDK from the source code. No human wrote this, it's giving robot main character energy πŸ€–βœ¨


And that's the whole page, bestie 🫢 β€” signed off from DPDK, Version 26.03.0, rte_regexdev_match(3). Periodt. πŸ’œ

πŸ“¦ where this page comes from