RTE_EVENT_CRYPTO_REQUEST(3)

💖 NAME 💖

rte_event_crypto_request — bestie, it's the crypto event request struct, and she's literally the whole plot ok ✨

She lives in the Library Functions Manual, which is a very serious place for a girlboss like her ngl 🎀

---

✨ SYNOPSIS ✨

#include <rte_event_crypto_adapter.h>

🦋 Data Fields

• uint8_t resv [8]
• uint16_t cdev_id
• uint16_t queue_pair_id
• uint32_t resv1

---

💅 DETAILED DESCRIPTION 💅

okay so here's the tea ☕ — this Crypto event request structure is the one your application fills in to hand over event request info to the adapter. That's it. That's the job. She's the messenger 🫶

Definition at line 204 of file rte_event_crypto_adapter.h.

---

👑 FIELD DOCUMENTATION 👑

🌸 uint8_t resv[8]

not me overlapping with the first 8 bytes of struct rte_event that encode the response event information 😭 that's literally what she does. Your application is expected to fill in struct rte_event response_info. periodt 💅

Definition at line 205 of file rte_event_crypto_adapter.h.

🌈 uint16_t cdev_id

the cryptodev ID to be used, bestie. that's the one. yep ✨

Definition at line 210 of file rte_event_crypto_adapter.h.

🍓 uint16_t queue_pair_id

the cryptodev queue pair ID to be used 💖 matching energies with cdev_id, iconic behavior tbh

Definition at line 212 of file rte_event_crypto_adapter.h.

🧚 uint32_t resv1

Reserved bits!! like, don't touch, she's saving those seats for later 🎀

Definition at line 214 of file rte_event_crypto_adapter.h.

---

💜 AUTHOR 💜

Generated automatically by Doxygen for DPDK from the source code. (she didn't write herself, the machines did, and honestly? slay 🤖💅)

---

k bye bestie 🫶 this whole page is from DPDK, Version 25.11.3, and yes the diva herself is rte_event_crypto_request(3) — no cap, that's the vibe check and she passed ⭐