rte_ml_dev_qp_conf(3)

✨ rte_ml_dev_qp_conf ✨

okay bestie so this is rte_ml_dev_qp_conf(3) β€” a library functions manual page from the DPDK crew πŸ’– it's a lil struct situation and honestly? she's giving "config girlie who holds your whole queue pair together". let's get into it 🫢


🌸 SYNOPSIS 🌸

#include <rte_mldev.h>

πŸŽ€ Data Fields

  • uint32_t nb_desc β€” how many descriptors live in each queue pair, periodt
  • rte_ml_dev_stop_flush_t cb β€” the callback function vibe, called during rte_ml_dev_stop()

πŸ’… Detailed Description

so like. this is the ML device queue pair configuration structure ✨ she's the blueprint, the main character energy of your QP setup, and she's defined at line 305 of the file rte_mldev.h πŸ’œ


πŸ¦‹ Field Documentation πŸ¦‹

uint32_t nb_desc

Number of descriptors per queue pair. that's it, that's the girl πŸ’…

⚠️ careful bestie β€” this value cannot exceed the max_desc which was previously provided in struct rte_ml_dev_info:max_desc. don't push past the limit, she said no cap fr fr 😭

defined at line 306 of the file rte_mldev.h πŸŽ€

rte_ml_dev_stop_flush_t cb

the callback function that gets called during rte_ml_dev_stop(), and she's invoked once per active ML op ⭐

a value of NULL is allowed! in which case the callback will not be invoked. lowkey a valid choice, no judgement πŸ’œ

what's she for? this function can be used to properly dispose of outstanding ML ops from all queue pairs β€” for example, ops that are holding memory pointers. very cleanup era, very responsible, we love to see it 🧹✨

See also

  • rte_ml_dev_stop()

defined at line 311 of the file rte_mldev.h 🌈


πŸ‘‘ Author

Generated automatically by Doxygen for DPDK from the source code 🫢 (not me writing a whole essay, bestie β€” the robots did this one, and honestly? slay πŸ€–πŸ’–)


kisses, this doc page lives in DPDK Version 25.11.3 and she's filed under rte_ml_dev_qp_conf(3) β€” go configure those queue pairs, you absolute icon πŸ’…πŸŒΈπŸ¦‹

πŸ“¦ where this page comes from