rte_bbdev_driver_info(3)

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

💖 NAME 💖

rte_bbdev_driver_info — bestie, this is a struct, okay? It's the lil info packet that a bbdev device's driver hands over so you know what the device can actually do. Live from the DPDK Library Functions Manual page. 🎀

✨ SYNOPSIS ✨

Pop this header in and you're in business, fr fr:

#include <rte_bbdev.h>

🦋 Data Fields 🦋

  • const char * driver_name
  • unsigned int max_num_queues
  • unsigned int num_queues [RTE_BBDEV_OP_TYPE_SIZE_MAX]
  • unsigned int queue_priority [RTE_BBDEV_OP_TYPE_SIZE_MAX]
  • uint32_t queue_size_lim
  • bool hardware_accelerated
  • uint8_t max_dl_queue_priority
  • uint8_t max_ul_queue_priority
  • bool queue_intr_supported
  • enum rte_bbdev_device_status device_status
  • uint32_t harq_buffer_size
  • uint16_t min_alignment
  • uint8_t data_endianness
  • struct rte_bbdev_queue_conf default_queue_conf
  • const struct rte_bbdev_op_cap * capabilities
  • enum rte_cpu_flag_t * cpu_flag_reqs
  • uint16_t * fft_window_width

🌸 DETAILED DESCRIPTION 🌸

Device information supplied by the device's driver. 💅 Like, it's the driver's "here's what I bring to the table" moment.

Definition at line 322 of file rte_bbdev.h.

🦋 FIELD DOCUMENTATION 🦋

Okay so here's the full breakdown, field by field, no skips, no cap. 🫶

const char* driver_name

Driver name. Simple as that. ✨

Definition at line 324 of file rte_bbdev.h.

unsigned int max_num_queues

Maximum number of queues supported by the device. 👑

Definition at line 327 of file rte_bbdev.h.

unsigned int num_queues[RTE_BBDEV_OP_TYPE_SIZE_MAX]

Maximum number of queues supported per operation type. That array index is not vibes, it's RTE_BBDEV_OP_TYPE_SIZE_MAX. 🍓

Definition at line 329 of file rte_bbdev.h.

unsigned int queue_priority[RTE_BBDEV_OP_TYPE_SIZE_MAX]

Priority level supported per operation type. Same array situation, same size constant. 💜

Definition at line 331 of file rte_bbdev.h.

uint32_t queue_size_lim

Queue size limit — and heads up bestie, the queue size must also be a power of 2. Both things. Not one or the other. 😭

Definition at line 333 of file rte_bbdev.h.

bool hardware_accelerated

Set if the device off-loads operation to hardware. 🚀

Definition at line 335 of file rte_bbdev.h.

uint8_t max_dl_queue_priority

Max value supported by queue priority for DL.

Definition at line 337 of file rte_bbdev.h.

uint8_t max_ul_queue_priority

Max value supported by queue priority for UL. Twin of the one above but for the uplink side. 🔥

Definition at line 339 of file rte_bbdev.h.

bool queue_intr_supported

Set if the device supports per-queue interrupts. ⚡

Definition at line 341 of file rte_bbdev.h.

enum rte_bbdev_device_status device_status

Device Status. That's it, that's the field. 💀

Definition at line 343 of file rte_bbdev.h.

uint32_t harq_buffer_size

HARQ memory available, measured in kB. 🎀

Definition at line 345 of file rte_bbdev.h.

uint16_t min_alignment

Minimum alignment of buffers, in bytes. Don't sleep on alignment bestie. 🌈

Definition at line 347 of file rte_bbdev.h.

uint8_t data_endianness

Byte endianness supported for input/output data — so, RTE_BIG_ENDIAN or RTE_LITTLE_ENDIAN. 🧚

Definition at line 351 of file rte_bbdev.h.

struct rte_bbdev_queue_conf default_queue_conf

Default queue configuration, used if none is supplied. It's giving "the fallback fit". ✨

Definition at line 353 of file rte_bbdev.h.

const struct rte_bbdev_op_cap* capabilities

Device operation capabilities. 🙈

Definition at line 355 of file rte_bbdev.h.

enum rte_cpu_flag_t* cpu_flag_reqs

Device cpu_flag requirements. Yes, requirements. Check them. 💜

Definition at line 357 of file rte_bbdev.h.

uint16_t* fft_window_width

FFT windowing width for 2048 FFT — size defined in capability. 🦋

Definition at line 359 of file rte_bbdev.h.

👑 AUTHOR 👑

Generated automatically by Doxygen for DPDK from the source code. (Yeah bestie, a robot wrote this, and honestly? It ate. 🤖💅)

Okay that's the whole page, mwah. 💖 This one came from DPDK, Version 25.11.3, and it's the rte_bbdev_driver_info(3) manual page — go off and read your driver info responsibly, periodt. 🎀✨🌸

📦 where this page comes from