rte_flow_error(3)

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

✨ NAME ✨

rte_flow_error — bestie, it's the verbose error struct from DPDK's flow API, and it's here to tell you exactly what went wrong 💅

🦋 SYNOPSIS 🦋

#include <rte_flow.h>

🎀 Data Fields 🎀

  • enum rte_flow_error_type type — the type, obviously, but also the cause field iykyk
  • const void * cause — the thing that did this. the culprit. the perpetrator 🙈
  • const char * message — the human-readable part, so you can, like, actually read it 💖

🌸 Detailed Description 🌸

okay so. this is the verbose error structure definition ✨ like, this is the one that comes with receipts.

Normally applications allocate this object, and the PMDs fill it in. The message points to a constant string — meaning the application does NOT need to free it, no cap, put the free() down 😌

BUT. and this is the important bit, listen up bestie 👑

That pointer is only valid as long as its associated DPDK port remains configured. Like, the moment you close the underlying device or unload the PMD? invalidated. gone. expired. the vibe check failed 💀 So don't go holding onto that pointer like it's a situationship you can text back in three weeks.

Also — and I cannot stress this enough — both cause and message may be NULL regardless of the error type. Yeah. Even if the type says something is wrong, those fields can still just be like... nothing. ghosted. 🫥

Definition lives at line 4378 of file rte_flow.h 📍

🔥 Field Documentation 🔥

💜 enum rte_flow_error_type type

cause field and error types — like, the ~categories~ of what went down.

Definition at line 4379 of file rte_flow.h.

🍓 const void* cause

object responsible for the error. the one who did this. the main character of the problem 😤

Definition at line 4380 of file rte_flow.h.

🧚 const char* message

human-readable error message. yes bestie, human-readable, unlike some error codes we could name 🌈

Definition at line 4381 of file rte_flow.h.

🌟 Author 🌟

Generated automatically by Doxygen for DPDK from the source code. not a human, not a girlboss, just a doc generator doing its thing 🤖✨

okay that's the whole page bestie, hope this was giving enlightenment 💖 This little scroll of knowledge is served up fresh from DPDK, Version 25.11.3, and that's the whole rte_flow_error(3) situation — mwah, slay, go forth and debug 🎀👑🦋

📦 where this page comes from