RESPONSE_INFO(3)

πŸ“¦ version 26.03, in nixos 26.05, nixpkgs unstable

πŸ’– NAME πŸ’–

rte_event_crypto_metadata β€” okay bestie, this is the glow-up name for the crypto event metadata struct, and yes it's literally the main character of this whole page 🫢


✨ SYNOPSIS ✨

Pull it in like this, no cap:

#include <rte_event_crypto_adapter.h>

πŸŽ€ Data Fields πŸŽ€

  • struct rte_event_crypto_request request_info
  • struct rte_event response_info

🌸 Detailed Description 🌸

So here's the vibe: this is the crypto event metadata structure, and you (the application) fill it in with crypto request info + event response info. It's giving "you do the homework, the struct holds the notes" πŸ“βœ¨

If crypto events get enqueued using a HW mechanism, the cryptodev PMD is the one that reads the event response information and uses it to set up the event that gets enqueued back to eventdev after the crypto operation finishes. Slay, hardware doing its own thing πŸ’…

But if the transfer is done by SW, then it's the adapter that uses the event response information instead. Different beastie, same info πŸ”₯

Lowkey important: this struct is defined at line 228 of rte_event_crypto_adapter.h β€” that's the receipts, iykyk πŸ’€

πŸŽ€ Field Documentation πŸŽ€

🌟 struct rte_event_crypto_request request_info

Request information that you, the application, fill in β€” specifically for RTE_EVENT_CRYPTO_ADAPTER_OP_FORWARD mode. And bestie, listen: the first 8 bytes of request_info are reserved for response_info, so don't go squishing your stuff in there πŸ™ˆ

Defined at line 229 of rte_event_crypto_adapter.h ✨

πŸ¦‹ struct rte_event response_info

Response information, again filled in by the application β€” this one covers both RTE_EVENT_CRYPTO_ADAPTER_OP_NEW and RTE_EVENT_CRYPTO_ADAPTER_OP_FORWARD mode. Two modes, one field, we love a versatile icon πŸ‘‘

Defined at line 234 of rte_event_crypto_adapter.h πŸ’–


πŸ’… Author πŸ’…

Generated automatically by Doxygen for DPDK from the source code β€” not me writing fanfic, it literally made itself 😭


✨ and that's the whole page, bestie ✨ This lil' manual moment came to you courtesy of DPDK, Version 26.03.0, under the rte_event_...to_metadata(3) tag β€” Library Functions Manual energy throughout πŸŽ€πŸ’œ Go forth and fill your metadata correctly, mwah πŸ’‹

πŸ“¦ where this page comes from