rte_ml_dev_config(3)

✨ NAME ✨

rte_ml_dev_config — bestie, this is the ML device configuration struct, from the DPDK libc crew (Library Functions Manual, section 3) 💅

---

🦋 SYNOPSIS 🦋

#include <rte_mldev.h>

📦 Data Fields

• int socket_id
• uint16_t nb_models
• uint16_t nb_queue_pairs

---

🌸 DETAILED DESCRIPTION 🌸

So. ML device configuration structure. That's the whole vibe, that's what it is 💖

Fr fr, this is the struct you fill in to tell an ML device how you want it set up. It lives at Definition at line 259 of file rte_mldev.h.

---

👑 FIELD DOCUMENTATION 👑

int socket_id

Socket to allocate resources on. Yes, the NUMA socket. Yes, it matters. 🫶

Definition at line 260 of file rte_mldev.h.

uint16_t nb_models

Number of models to be loaded on the device. Lowkey important: this value cannot exceed the max_models which is previously provided in struct rte_ml_dev_info::max_models. So check your info struct first, don't just yeet a number in there 😭

Definition at line 262 of file rte_mldev.h.

uint16_t nb_queue_pairs

Number of queue pairs to configure on this device. And heads up bestie: this value cannot exceed the max_models which is previously provided in struct rte_ml_dev_info::max_queue_pairs. (Yes, max_models — that is literally what the docs say, I am not editing the source, don't @ me 💀)

Definition at line 267 of file rte_mldev.h.

---

🎀 AUTHOR 🎀

Generated automatically by Doxygen for DPDK from the source code. Not a human, not a bestie, just a very productive robot 🤖✨

---

okay that's the whole page, mwah 💜 go config your devices, you're doing amazing, and remember: it's all DPDK, Version 25.11.3, and this iconic little doc came to you from the rte_ml_dev_config(3) manual page — periodt 🎀🌸🦋👑