rte_regexdev_core.h(3)

💖 NAME 💖

rte_regexdev_core.h — bestie, it's the internal RegEx device header, and no, it's not for you (affectionately) 💅

---

✨ SYNOPSIS ✨

🎀 Data Structures 🎀

struct rte_regexdev_ops

🦋 Enumerations 🦋

enum rte_regexdev_state {
    RTE_REGEXDEV_UNUSED = 0,
    RTE_REGEXDEV_REGISTERED,
    RTE_REGEXDEV_READY
}

---

🌸 DETAILED DESCRIPTION 🌸

Okay so — this is the RTE RegEx Device internal header. It's giving backstage-pass energy: it holds the internal data types that the RegEx devices use to expose their ops to the class. Like, the whole plumbing situation. 🔧

HARD WARNING bestie: Applications should not use these API directly. Fr fr. This is not your lane, this is the device driver's lane. Hands off the wheel 💀

For the record, this is defined in the file rte_regexdev_core.h. Periodt. 👑

---

🌈 ENUMERATION TYPE DOCUMENTATION 🌈

enum rte_regexdev_state

The possible states of a RegEx device — its whole mood ring, basically. 🔮

Enumerator

• RTE_REGEXDEV_UNUSED — the device is unused. Just sittin' there, no thoughts, head empty. 🙈
• RTE_REGEXDEV_REGISTERED — the device is registered, but not ready to be used. Like, it exists, it has a name, but it is not serving yet. It's in its waiting room era. ⏳
• RTE_REGEXDEV_READY — the device is ready for use. And lowkey important detail: this one is set by the PMD. So if it says ready, the PMD said so. Slay. 🔥

Defined right there at line 132 of the file rte_regexdev_core.h. Mark it, iykyk. 📍

---

💜 AUTHOR 💜

Generated automatically by Doxygen for DPDK from the source code. Not a human, just a robot doing its little robot thing and honestly? It ate. 🫶

---

That's the whole vibe check, bestie 💖 this page came from DPDK, Version 25.11.3, and it's the rte_regexdev_core.h(3) page from the Library Functions Manual — a.k.a. section 3, where all the library function lore lives. Go forth and do NOT call these APIs directly. Mwah 🎀✨