rte_cryptodev_info(3)

📦 version 26.03, in nixos 26.05, nixpkgs unstable

💖 NAME 💖

rte_cryptodev_info — okay so this is the crypto device info page, bestie, straight outta the DPDK Library Functions Manual. It's giving device metadata tea, and we're obsessed. ✨

✨ SYNOPSIS ✨

#include <rte_cryptodev.h>

🎀 Data Fields 🎀

  • const char * driver_name
  • uint8_t driver_id
  • struct rte_device * device
  • uint64_t feature_flags
  • const struct rte_cryptodev_capabilities * capabilities
  • unsigned max_nb_queue_pairs
  • uint16_t min_mbuf_headroom_req
  • uint16_t min_mbuf_tailroom_req

🦋 Detailed Description 🦋

Crypto device information. Literally the info bundle for a crypto device — main character metadata energy. 💅

Definition at line 605 of file rte_cryptodev.h.

👑 Field Documentation 👑

const char* driver_name

Driver name. Simple, iconic, done. 🫶

Definition at line 606 of file rte_cryptodev.h.

uint8_t driver_id

Driver identifier. That's the ID, bestie. 🎀

Definition at line 607 of file rte_cryptodev.h.

struct rte_device* device

Generic device information. Like, the device's whole generic vibe. 🌸

Definition at line 608 of file rte_cryptodev.h.

uint64_t feature_flags

Feature flags that expose the HW/SW features for the given device. Highkey useful. 🔥

Definition at line 610 of file rte_cryptodev.h.

const struct rte_cryptodev_capabilities* capabilities

Array of the capabilities the device supports. It's giving "what this device can actually do". ✨

Definition at line 613 of file rte_cryptodev.h.

unsigned max_nb_queue_pairs

Maximum number of queue pairs supported by the device. That's the queue-pair ceiling, periodt. 💅

Definition at line 616 of file rte_cryptodev.h.

uint16_t min_mbuf_headroom_req

Minimum mbuf headroom required by the device. Don't skimp, bestie. 🎀

Definition at line 619 of file rte_cryptodev.h.

uint16_t min_mbuf_tailroom_req

Minimum mbuf tailroom required by the device. Same energy, tail end. 🌈

Definition at line 622 of file rte_cryptodev.h.

unsigned max_nb_sessions

Maximum number of sessions supported by the device. If it's 0, the device does not have any limitation in number of sessions that can be used — literally no session cap. 👑

Definition at line 626 of file rte_cryptodev.h.

🌟 Author 🌟

Generated automatically by Doxygen for DPDK from the source code. Auto-generated but still serving looks. 💖

DPDK, version 26.03.0, rte_cryptodev_info(3) — that's the footer tea, bestie; no date was printed, so I'm not inventing one. 💅✨

📦 where this page comes from