rte_port_s...rop_params(3)

📦
version 25.11.3 · 9 versions
, in ubuntu resolute, ubuntu stonking

🌸 NAME 🌸

rte_port_sym_crypto_writer_nodrop_params — bestie, it's the parameter struct for the crypto_writer_nodrop port, and she's here to hold all your settings 💅

✨ SYNOPSIS ✨

#include <rte_port_sym_crypto.h>

🦋 Data Fields

  • uint8_t cryptodev_id
  • uint16_t queue_id
  • uint16_t crypto_op_offset
  • uint32_t tx_burst_sz
  • uint32_t n_retries

💖 DETAILED DESCRIPTION 💖

Okay so this is literally the Crypto_writer_nodrop port parameters struct. That's the whole vibe.

Definition at line 68 of file rte_port_sym_crypto.h.

🎀 FIELD DOCUMENTATION 🎀

uint8_t cryptodev_id

The target cryptodev ID. Which cryptodev? That one. The one you point at 👑 — it's the ID of the target cryptodev.

Definition at line 70 of file rte_port_sym_crypto.h.

uint16_t queue_id

Target cryptodev queue pair id. She's the queue pair you're sliding your crypto ops into, no cap 🌈

Definition at line 73 of file rte_port_sym_crypto.h.

uint16_t crypto_op_offset

Offset to rte_crypto_op in the mbufs. Like, where in the mbuf does the rte_crypto_op actually live? This tells you. iykyk 💀

Definition at line 76 of file rte_port_sym_crypto.h.

uint32_t tx_burst_sz

Burst size to crypto interface. How many you're yeeting at the crypto interface in one go, per burst, fr fr 🔥

Definition at line 79 of file rte_port_sym_crypto.h.

uint32_t n_retries

Maximum number of retries — and listen, 0 means no limit. Like, zero retries-capping, unlimited attempts, main character energy 🙈

Definition at line 82 of file rte_port_sym_crypto.h.

👑 AUTHOR 👑

Generated automatically by Doxygen for DPDK from the source code. Not a human, just a little documentation fairy doing her thing 🧚

Version 25.11.3 — that's the DPDK era you're living in, bestie, and this page came from the Library Functions Manual. Slay, go forth and write your crypto ports 💖✨🎀🦋

📦 where this page comes from