RESV1(3)

📦 version 26.03, in nixos 26.05, nixpkgs unstable

🌸 NAME 🌸

rte_event_crypto_request — okay bestie, welcome to the rte_event_crypto_request(3) page from the Library Functions Manual ✨ This is the crypto event request structure page, and we're gonna get you comfy with every single field, no cap 💅

✨ SYNOPSIS ✨

#include <rte_event_crypto_adapter.h>

📦 Data Fields 📦

The data fields are giving:

  • uint8_t resv [8]
  • uint16_t cdev_id
  • uint16_t queue_pair_id
  • uint32_t resv1

💖 Detailed Description 💖

Okay so here's the tea: the crypto event request structure will be filled by the application to provide event request information to the adapter. That's the whole vibe — app fills it in, adapter gets the info 🫶

📍 Definition at line 204 of file rte_event_crypto_adapter.h.

🎀 Field Documentation 🎀

🧚 uint8_t resv[8]

Bestie, this one overlaps with the first 8 bytes of struct rte_event — specifically the bytes that encode the response event information. The application is expected to fill in struct rte_event response_info. So yeah, it's doing double duty, and it ate 💅

📍 Definition at line 205 of file rte_event_crypto_adapter.h.

🔥 uint16_t cdev_id

The cryptodev ID to be used. That's it, that's the field — iconic, concise, no notes 👑

📍 Definition at line 210 of file rte_event_crypto_adapter.h.

🌸 uint16_t queue_pair_id

The cryptodev queue pair ID to be used. Queue pair match energy, fr fr 🦋

📍 Definition at line 212 of file rte_event_crypto_adapter.h.

💜 uint32_t resv1

Reserved bits. Just reserved bits, hanging out and being reserved — no cap 🙈

📍 Definition at line 214 of file rte_event_crypto_adapter.h.

🌈 Author 🌈

Generated automatically by Doxygen for DPDK from the source code.

Okay bestie, that's the whole page! This cutie comes from DPDK, Version 26.03.0, and the footer also has rte_event_crypto_request(3) — and there's no date listed, so we're not inventing one, periodt. Bye bestie, go slay those crypto event requests 💖✨🎀

📦 where this page comes from