RETVAL(3)

📦 version 26.03, in nixos 26.05, nixpkgs unstable

💅 Library Functions Manual — rte_pmd_i40e_mb_event_param(3) 💅

okay so bestie, this is the rte_pmd_i40e_mb_event_param page from the Library Functions Manual. The terminal header/footer tag is abbreviated as rte_pmd_i4...event_param(3) — yes, the truncation is giving chaos, but we move. 🫶

🌸 NAME 🌸

rte_pmd_i40e_mb_event_param — the data-fields page for the stuff sent to the user application when the callback is executed ✨

✨ SYNOPSIS ✨

#include <rte_pmd_i40e.h>

🎀 Data Fields 🎀

  • uint16_t vfid
  • uint16_t msg_type
  • uint16_t retval
  • void * msg
  • uint16_t msglen

💖 Detailed Description 💖

Data sent to the user application when the callback is executed. That's the whole vibe — this is the payload situation for your callback. 💌

Definition at line 38 of file rte_pmd_i40e.h.

🦋 Field Documentation 🦋

💜 uint16_t vfid 💜

Virtual Function number. Very demure, very VF-coded. 🧚

Definition at line 39 of file rte_pmd_i40e.h.

🎀 uint16_t msg_type 🎀

VF to PF message type, see virtchnl_ops. iykyk 👑

Definition at line 40 of file rte_pmd_i40e.h.

🍓 uint16_t retval 🍓

return value. Literally the return value, no cap. 💅

Definition at line 41 of file rte_pmd_i40e.h.

🦋 void* msg 🦋

pointer to message. It points at the message, bestie — that's the whole job. 📬

Definition at line 42 of file rte_pmd_i40e.h.

🌈 uint16_t msglen 🌈

length of the message. Gotta know how long the message is, periodt. 📏

Definition at line 43 of file rte_pmd_i40e.h.

👑 Author 👑

Generated automatically by Doxygen for DPDK from the source code. Not a human author moment — it's giving automation slay. 🤖✨

mwah 💋 — the footer energy is DPDK, Version 26.03.0, with the page tag rte_pmd_i4...event_param(3). That's the version/date slot from the bottom of the page, preserved and cute. 🎀

📦 where this page comes from