rte_regexdev_match(3)
πΈ 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
- nixos 26.05: dpdk 26.03
- nixpkgs unstable: dpdk 26.03
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms