rte_pie_config(3)

πŸ’– rte_pie_config(3) πŸ’–

okay bestie, welcome to the rte_pie_config page β€” it lives in the Library Functions Manual, section 3, and it's literally just the struct that holds all your PIE config vibes. no cap.


✨ NAME ✨

rte_pie_config β€” the configuration parameters struct, she's iconic, she's a struct, she holds the settings.


🌸 SYNOPSIS 🌸

#include <rte_pie.h>

πŸŽ€ Data Fields πŸŽ€

  • uint64_t qdelay_ref
  • uint64_t dp_update_interval
  • uint64_t max_burst
  • uint16_t tailq_th

πŸ’… Detailed Description πŸ’…

PIE configuration parameters πŸ’–

fr fr, that's the whole mood. her definition lives at line 45 of the file rte_pie.h. slay.


πŸ¦‹ Field Documentation πŸ¦‹

uint64_t qdelay_ref πŸ‘‘

Latency Target β€” measured in CPU cycles.

Definition at line 46 of file rte_pie.h.

uint64_t dp_update_interval ⏰

Update interval for drop probability β€” also in CPU cycles, bestie, don't forget the units or she will not behave.

Definition at line 47 of file rte_pie.h.

uint64_t max_burst πŸ“

Max Burst Allowance β€” yep, in CPU cycles. again. it's giving consistency.

Definition at line 48 of file rte_pie.h.

uint16_t tailq_th 🌈

Tailq drop threshold β€” this one's in packet counts, not cycles, so pay attention diva, different unit entirely.

Definition at line 49 of file rte_pie.h.


⚠️ heads up: qdelay_ref, dp_update_interval, and max_burst are all counted in CPU cycles, while tailq_th counts packets. mixing those up is not the vibe. πŸ’€

πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for DPDK from the source code. not a human author, just a robot doing her best 🫢


and that's the whole page, bestie! this one came from DPDK, Version 25.11.3, under the manual entry rte_pie_config(3). mwah, go configure some queues responsibly πŸ’–βœ¨

πŸ“¦ where this page comes from