rte_regexdev_config(3)

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

💖 rte_regexdev_config(3) 💖

okay bestie, so this is a library functions manual page for rte_regexdev_config — it's the whole lore on the RegEx device configuration struct. it lives in rte_regexdev.h and it's basically the lil form you fill out to tell a RegEx device how you want it set up. no cap, let's get into it. ✨

🌸 NAME 🌸

rte_regexdev_config — the RegEx device configuration structure, and the star of this whole page 🎀

✨ SYNOPSIS ✨

#include <rte_regexdev.h>

🦋 Data Fields 🦋

  • uint16_t nb_max_matches
  • uint16_t nb_queue_pairs
  • uint32_t nb_rules_per_group
  • uint16_t nb_groups
  • const char * rule_db
  • uint32_t rule_db_len
  • uint32_t dev_cfg_flags

💅 Detailed Description 💅

it's a RegEx device configuration structure 🫶

Definition at line 679 of file rte_regexdev.h.

👑 Field Documentation 👑

⭐ uint16_t nb_max_matches

the max matches per scan you're configuring on this device, babe. this value cannot exceed the max_matches that you previously handed over in rte_regexdev_info_get(). and yes, the value 0 is allowed — in that case, the value 1 is used. so if you thought 0 meant "none", nope, it means one. 😭

See also

  • struct rte_regexdev_info::max_matches
Definition at line 680 of file rte_regexdev.h.

⭐ uint16_t nb_queue_pairs

how many RegEx queue pairs you want configured on this device. this value cannot exceed the max_queue_pairs which you previously provided in rte_regexdev_info_get(). that's the vibe check — stay under the ceiling fr fr. 💀

See also

  • struct rte_regexdev_info::max_queue_pairs
Definition at line 687 of file rte_regexdev.h.

⭐ uint32_t nb_rules_per_group

how many rules per group you're configuring on this device. this value cannot exceed the max_rules_per_group which you previously provided in rte_regexdev_info_get(). and the value 0 is allowed here too — in which case, struct rte_regexdev_info::max_rules_per_group is used. so 0 is giving "girl just use the default" and honestly? iconic. 💅

See also

  • struct rte_regexdev_info::max_rules_per_group
Definition at line 693 of file rte_regexdev.h.

⭐ uint16_t nb_groups

how many groups you're configuring on this device. this value cannot exceed the max_groups which you previously provided in rte_regexdev_info_get(). keep it in range bestie. 🎀

See also

  • struct rte_regexdev_info::max_groups
Definition at line 701 of file rte_regexdev.h.

⭐ const char* rule_db

this one imports the initial set of prebuilt rule database onto this device. the value NULL is allowed — in which case, the device will not be configured with a prebuilt rule database. and don't stress, your application may use rte_regexdev_rule_db_update() or rte_regexdev_rule_db_import() API to update or import the rule database after the rte_regexdev_configure(). see? you have options. we love options. 🦋

See also

  • rte_regexdev_rule_db_update()
  • rte_regexdev_rule_db_import()
Definition at line 707 of file rte_regexdev.h.

⭐ uint32_t rule_db_len

the length of the rule_db buffer. short and sweet, that's all she said. 💖

Definition at line 716 of file rte_regexdev.h.

⭐ uint32_t dev_cfg_flags

the RegEx device configuration flags — See RTE_REGEXDEV_CFG_* for the deets. 🌈

Definition at line 718 of file rte_regexdev.h.

🫶 Author 🫶

Generated automatically by Doxygen for DPDK from the source code. (not a human, just a very diligent robot doing its lil thing 🧚)

and that's the whole page bestie, slay. this gorgeous lil doc is from DPDK, Version 25.11.3, no cap 💜 periodt ✨

📦 where this page comes from