iavf_fill_fdir_pfcp_hdr(9)

📦 version 7.3.1, in nixpkgs unstable

💅 iavf_fill_fdir_pfcp_hdr — the PFCP header glow-up function ✨

Okay bestie, so this is a page from the Kernel API Manual (section 9, kernel developer vibes only 🧚), and it's all about one lil helper: iavf_fill_fdir_pfcp_hdr. She's the one who fills in the PFCP protocol header. Iconic, focused, does one thing. We love a specialist 👑

🌸 NAME 🌸

iavf_fill_fdir_pfcp_hdr — fill the PFCP protocol header 💖

Like, that's literally her whole job. She fills the PFCP header. No cap.

✨ SYNOPSIS ✨

int iavf_fill_fdir_pfcp_hdr (struct iavf_fdir_fltr *fltr , struct
       virtchnl_proto_hdrs *proto_hdrs );

So she takes two things and hands you back an int. Short signature, big main character energy 🫶

🎀 ARGUMENTS 🎀

  • fltr — the Flow Director filter data structure 🦋 like, the filter itself, the whole point of the operation
  • proto_hdrs — the Flow Director protocol headers data structure 🌈 this is the header situation getting filled in

Two structs, one mission. Slay.

💜 DESCRIPTION 💜

Returns 0 if the PFCP protocol header is set successfully ✅

That's it. That's the whole description. Zero means "yes bestie, it worked." Not gonna overcomplicate it — sometimes a function is just straightforward and emotionally stable 💅

🔥 SEE ALSO 🔥

Look at that whole friend group 😭 every iavf_fill_fdir_*_hdr(9) sibling is here — the eth one, the ip4 one, the ip6 one, the tcp/udp/sctp ones, the ah/esp ones, the l4 one, the gtpu and nat_t_esp and udp_flex_pay ones. A whole squad of header fillers and she's just one of them, living her truth 🧚‍♀️

💀 Tiny page, tiny function — but she still returns 0 on success and nothing else is documented here, so don't go inventing extra behaviour, bestie. Facts only, always 🫶

And that's a wrap, bestie! This page came to you from the kernel source tree at ./drivers/net/ethernet/intel/iavf, dated October 2026, and it's the iavf_fill_fdir_pfcp_hdr(9) page — go fill some PFCP headers, you absolute icon 👑💖🎀

📦 where this page comes from