rte_flow_error(3)

📦 version 26.03, in nixos 26.05, nixpkgs unstable

🌸 NAME 🌸

So this is the rte_flow_error(3) page from the Library Functions Manual, bestie, and it's literally all about rte_flow_error — the verbose error struct. No cap, it's giving “error info but make it structured.” 💅

✨ SYNOPSIS ✨

#include <rte_flow.h>

🎀 Data Fields 🎀

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

💖 DETAILED DESCRIPTION 💖

Okay so rte_flow_error is the verbose error structure definition. Main character energy for error reporting, honestly. ✨

This object is normally allocated by applications and set by PMDs. The message points to a constant string, and the application does not need to free it — but its pointer can be considered valid only as long as its associated DPDK port remains configured. Closing the underlying device or unloading the PMD invalidates it. That part is important, bestie — don't hold onto that pointer after the port goes away. 😭

Both cause and message may be NULL regardless of the error type. So yes, they can absolutely be NULL, and that's valid. 🫶

Definition at line 4377 of file rte_flow.h.

🫶 FIELD DOCUMENTATION 🫶

⭐ enum rte_flow_error_type type

Cause field and error types.

Definition at line 4378 of file rte_flow.h.

⭐ const void* cause

Object responsible for the error.

Definition at line 4379 of file rte_flow.h.

⭐ const char* message

Human-readable error message.

Definition at line 4380 of file rte_flow.h.

👑 AUTHOR 👑

Generated automatically by Doxygen for DPDK from the source code.

That's the whole page, bestie — DPDK, Version 26.03.0, and rte_flow_error(3) signing off with immaculate error-struct vibes. Periodt. 💖✨🎀

📦 where this page comes from