RTE_EVENT_CRYPTO_METADATA(3)
π NAME π
rte_event_crypto_metadata β the lil glow-up struct that carries your crypto request deets and your event response deets, bestie π«Ά
β¨ SYNOPSIS β¨
#include <rte_event_crypto_adapter.h>
πΈ Data Fields
struct rte_event_crypto_request request_infostruct rte_event response_info
π¦ DESCRIPTION π¦
Okay so picture this: this is the crypto event metadata structure, and it's literally empty until you β yes you, the application π«΅ β fill it in. It's giving "carry my crypto request info and my event response info, pls and thank you."
Here's the tea on who reads it:
- If crypto events get enqueued using a HW mechanism, the cryptodev PMD picks up that event response information to set up the event that gets enqueued back to the eventdev once the crypto operation is done. So like, the hardware does the whole thing behind your back (affectionate).
- But if the transfer is done by SW, then it's the adapter that uses the event response information instead.
Either way, somebody's reading your homework. π
Definition at line228of filerte_event_crypto_adapter.h. Periodt.
π FIELD DOCUMENTATION π
π struct rte_event_crypto_request request_info
Request information β and this one is filled in by the application for RTE_EVENT_CRYPTO_ADAPTER_OP_FORWARD mode. π
But hold up, listen: the first 8 bytes of request_info are reserved for response_info. So don't go touching those, they're spoken for. π«
Definition at line229of filerte_event_crypto_adapter.h.
π struct rte_event response_info
Response information β also filled in by the application, but this time it's for both RTE_EVENT_CRYPTO_ADAPTER_OP_NEW and RTE_EVENT_CRYPTO_ADAPTER_OP_FORWARD mode. Versatile icon behavior, honestly. β¨
Definition at line234of filerte_event_crypto_adapter.h.
π AUTHOR π
Bestie this was generated automatically by Doxygen for DPDK from the source code β so nobody's hand-wrote this, the robot did it and honestly? it ate. π€π
okay that's the whole page, mwah π This iconic lil doc is from DPDK, Version 25.11.3, and the page itself is rte_event_...to_metadata(3) β go forth and enqueue responsibly, my love π§π
π¦ where this page comes from
- ubuntu resolute: dpdk-doc 25.11.3-0ubuntu0.26.04.1 Β· BSD-3-Clause
- ubuntu stonking: dpdk-doc 25.11.3-1 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms