rte_tm_error(3)

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

💖 rte_tm_error(3) — Library Functions Manual 💖

okay bestie, pull up a chair, we're doing a manpage from the rte_tm_error(3) corner of the DPDK library functions manual and honestly? it's giving ✨verbose error structure✨ and i'm obsessed 🫶

🌸 NAME 🌸

rte_tm_error — the lil struct that holds your traffic-manager oopsie info 💅

✨ SYNOPSIS ✨

#include <rte_tm.h>

🎀 Data Fields

  • enum rte_tm_error_type type
  • const void * cause
  • const char * message

🦋 DETAILED DESCRIPTION 🦋

so like, this is the verbose error structure definition — a whole glow-up of an error object that actually tells you things instead of just going "nope 💀".

Here's the tea: this object is normally allocated by applications and set by PMDs. The message points at a constant string, and the good news is the application does not need to free it — no cap, no cleanup duty for you, bestie 🙈.

BUT. and this is the important part, so listen up 👑 — that pointer can only be considered valid as long as its associated DPDK port remains configured. So if you close the underlying device, or unload the PMD? boom. invalidated. the pointer is done, it's not coming back, the vibe is over 😭.

Also both cause and message may be NULL regardless of the error type. so don't go dereferencing them without a check, fr fr.

Definition at line 1218 of file rte_tm.h. 📍

💅 FIELD DOCUMENTATION 💅

enum rte_tm_error_type type

what caused it + which error type it is. the cause field and the error type, two jobs, one enum, main character energy fr.

Definition at line 1219 of file rte_tm.h. 📍

const void* cause

the actual object responsible for the error 🔥 like, who did this. point directly at the culprit, no subtweets.

Definition at line 1220 of file rte_tm.h. 📍

const char* message

the human-readable error message 🎀 you know, words. for humans. so you can read what went wrong instead of decoding a mystery number.

Definition at line 1221 of file rte_tm.h. 📍

🌈 AUTHOR 🌈

Generated automatically by Doxygen for DPDK from the source code. so nobody hand-wrote this, a robot did it, and honestly? slay, Doxygen ate that 💖

alright bestie, that's a wrap on rte_tm_error from the DPDK Version 25.11.3 manual — mwah, go configure your ports and keep your pointers in check, ily, bye 🩷✨🧚

📦 where this page comes from