QUEUE_INFO(3)

📦 version 26.03, in nixos 26.05, nixpkgs unstable

💖 NAME 💖

rte_pmd_mlx5_driver_event_cb_queue_info — bestie, this is a whole struct (lowkey the documentation page for all its fields) from the DPDK Library Functions Manual, and it's the little info bundle that tells you everything about the queue whenever a driver event fires ✨

🌸 SYNOPSIS 🌸

Include it like this, okay?

#include <rte_pmd_mlx5.h>

🎀 Data Fields

  • uint16_t dpdk_queue_id
  • uint32_t hw_queue_id
  • const char * queue_info

🦋 DESCRIPTION 🦋

Okay so picture this: a driver event just got called, right? And you're like "wait, which queue even is this??" — that's literally what this struct is for 💅 It holds information about the queue for which the driver event is being called.

It's defined at line 436 of the file rte_pmd_mlx5.h. Slay.

👑 FIELD DOCUMENTATION 👑

⭐ uint16_t dpdk_queue_id

The DPDK queue index, periodt. ✨

Fr fr, this one lives at line 438 of rte_pmd_mlx5.h.

💜 uint32_t hw_queue_id

The HW queue identifier (that's the DevX object ID, iykyk) 🫶

Also chilling at line 440 of rte_pmd_mlx5.h.

🌈 const char* queue_info

The low-level HW configuration of the port related to the queue, and no cap it comes as a string of "key=value" pairs separated by commas 🍓

⚠️ Listen up bestie: this string is owned by mlx5 PMD — you should NOT free it yourself, and you should copy it into memory that you own. Not me warning you twice. Okay maybe I am. 💀

For RTE_PMD_MLX5_DRIVER_EVENT_CB_TYPE_RXQ_CREATE this will contain:

  • lro_timeout — the configured timeout of the LRO session in microseconds. Set to 0 if LRO is not configured.
  • max_lro_msg_size — the maximum size of a single LRO message. Provided in granularity of 256 bytes. Set to 0 if LRO is not configured.
  • td — identifier of transport domain allocated from HW (DevX object ID).
  • lbpk — set to 1 if loopback is enabled on the given queue.

For all other events, this field will be set to NULL 🙈

Definition's at line 460 of rte_pmd_mlx5.h, mwah 💋

🧚 AUTHOR 🧚

Generated automatically by Doxygen for DPDK straight from the source code — the robot wrote it so you don't have to 🎀

That's the whole vibe, bestie — this page came to you courtesy of DPDK, Version 26.03.0 in the Library Functions Manual, and yes, the header up top literally reads rte_pmd_ml..._queue_info(3) because even manpage titles get truncated sometimes 😭💖 ily, go read your driver events 🫶

📦 where this page comes from