rte_cryptodev_cb(3)

✨ NAME ✨

rte_cryptodev_cb β€” bestie, this is the lil struct that holds all the callback gossip for a queue pair πŸ’…


🫢 SYNOPSIS 🫢

#include <rte_cryptodev.h>

πŸ“¦ Data Fields

  • struct rte_cryptodev_cb * next
  • rte_cryptodev_callback_fn fn
  • void * arg

πŸ’– Detailed Description πŸ’–

Okay so picture this: it's a structure, and its whole entire job β€” its main character purpose, fr fr β€” is to hold information about the callbacks that get called for a queue pair on enqueue/dequeue. That's it. That's the vibe. She's not doing anything extra, she's just the carrier bag for callback deets πŸŽ€

It lives at Definition at line 1058 of file rte_cryptodev.h. β€” so go visit her there if you want. iykyk ✨

πŸ” Field Documentation πŸ”

🌸 struct rte_cryptodev_cb* next

A pointer to the next callback. She knows a girl who knows a girl πŸ¦‹ literally, linked-list style.

Definition at line 1059 of file rte_cryptodev.h.

🌈 rte_cryptodev_callback_fn fn

A pointer to the callback function itself. This is the one that actually does the thing when the moment comes, no cap πŸ”₯

Definition at line 1061 of file rte_cryptodev.h.

πŸ“ void* arg

A pointer to the argument. Just the lil bag of stuff you're passing along to her, lowkey essential 🌸

Definition at line 1063 of file rte_cryptodev.h.


πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for DPDK from the source code. Not a human, not a girlie, just a robot doing her best and honestly? she ate πŸ’…


okay that's the whole page bestie, mwah 🫢 this came out of the DPDK docs, Version 25.11.3, and yeah the header date situation is what it is β€” no date on the original footer, so no date from me, periodt. rte_cryptodev_cb(3) out πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from