rte_cryptodev_scheduler(3)

πŸ’– NAME πŸ’–

rte_cryptodev_scheduler β€” bestie, this is a library function manual page from the DPDK crew, and it's all about the lil struct that describes a cryptodev scheduler mode πŸŽ€


✨ SYNOPSIS ✨

Okay so first things first, you gotta pull in the header, periodt:

#include <rte_cryptodev_scheduler.h>

πŸ¦‹ Data Fields πŸ¦‹

Here's the whole squad of fields, no cap:

  • const char * name
  • const char * description
  • enum rte_cryptodev_scheduler_mode mode
  • struct rte_cryptodev_scheduler_ops * ops

🌸 Detailed Description 🌸

So like… this is the data structure associated with each mode of scheduler. That's literally it, that's the vibe β€” one struct per scheduler mode, living its main character life πŸ’…

Definition at line 262 of file rte_cryptodev_scheduler.h.

πŸ‘‘ Field Documentation πŸ‘‘

⭐ const char* name

The scheduler's name, duh. Like, what do we even call this thing? 🫢

Definition at line 263 of file rte_cryptodev_scheduler.h.

⭐ const char* description

The scheduler's description β€” the little blurb, the vibe check in words πŸ“

Definition at line 264 of file rte_cryptodev_scheduler.h.

⭐ enum rte_cryptodev_scheduler_mode mode

The scheduling mode. Which mode are we in, bestie?? That one πŸŒ€

Definition at line 265 of file rte_cryptodev_scheduler.h.

⭐ struct rte_cryptodev_scheduler_ops* ops

A pointer to the scheduler operation structure β€” like, the actual functions this bad boy runs. Obsessed πŸ”₯

Definition at line 268 of file rte_cryptodev_scheduler.h.

πŸŽ€ Author πŸŽ€

"Generated automatically by Doxygen for DPDK from the source code." β€” so yeah, no human wrote this one, it's a robot's glow-up πŸ€–βœ¨ not me getting emotional over autogenerated docs 😭


And that's a wrap, bestie! This lil page came to you from DPDK, Version 25.11.3, under the manual name rte_cryptodev_scheduler(3) πŸ’œ Stay slaying, keep your structs tight, and may your schedulers always schedule πŸŒˆπŸ¦‹

πŸ“¦ where this page comes from