iavf_fill_fdir_add_msg(9)

📦 version 7.3.1, in nixpkgs unstable

✨ iavf_fill_fdir_add_msg — the glow-up page ✨

okay so bestie, welcome to page 9 of the Kernel API Manual — yes the whole thing is filed under iavf_fill_fdir_add_msg(9) and it's giving "tiny function, big résumé" energy 💅

🎀 NAME 🎀

iavf_fill_fdir_add_msg — fill the Flow Director filter into the virtchnl message 🦋

Like, that's literally her whole job. She takes the filter and gets it all cozy inside the virtchnl message. No cap.

✨ SYNOPSIS ✨

int iavf_fill_fdir_add_msg (struct iavf_adapter *adapter , struct
iavf_fdir_fltr *fltr );

she returns an int, she takes two pointers, she's booked and busy 🫶

💖 ARGUMENTS 💖

  • adapter — pointer to the VF adapter structure 🧚 like, the whole VF adapter vibe, she needs the address of it
  • fltr — Flow Director filter data structure 🌸 the actual filter data, handing over her info

🔥 DESCRIPTION 🔥

Returns 0 if the add Flow Director virtchnl message is filled successfully ⭐

that's it, that's the whole personality. zero means she ate and left no crumbs 👑

🌈 SEE ALSO 🌈

first up, the kernel file she lives in, in case you wanna go snooping:

  • ./drivers/net/ethernet/intel/iavf/iavf_fdir.c 📁

and then the whole friend group, because she does not exist in a vacuum:

all of them are header-filling icons in their own right, iykyk 💜

real talk though bestie: this page tells you exactly one thing about what comes back — 0 when the message is filled successfully. anything else in the world of return values? not on this page. don't be out here inventing lore 🙈

and that's the tea 🍓 this lil masterpiece is served fresh from ./drivers/net/ethernet/intel/iavf, dated October 2026, page iavf_fill_fdir_add_msg(9). go be great, mwah 💋💖

📦 where this page comes from