fm10k_request_lport_map_pf(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ fm10k_request_lport_map_pf(9) ✨

okay bestie, buckle up πŸ’– this one lives in the Kernel API Manual, and honestly? it's a lil one. a tiny icon. a single-purpose queen πŸ‘‘


🌸 NAME 🌸

fm10k_request_lport_map_pf β€” literally just Request LPORT map from the switch API πŸ¦‹

that's it. that's the whole job. she asks the switch API for an LPORT map and she goes home. no cap.


✨ SYNOPSIS ✨

s32 fm10k_request_lport_map_pf (struct fm10k_hw *hw );

so she takes exactly one (1) thing and she gives you back an s32 πŸŽ€ periodt.


πŸ’… ARGUMENTS πŸ’…

  • hw β€” pointer to hardware structure πŸ‘‘ that's the whole parameter list, bestie. one pointer. to the hardware struct. nothing else. she's low-maintenance like that.

🫢 SEE ALSO 🫢

the friend group!! the whole fm10k_pf.c squad, fr fr 😭 and listen, we're not skipping a single one of them, everyone gets their name in the group chat:

first up, the source of truth β€” Kernel file ./drivers/net/ethernet/intel/fm10k/fm10k_pf.c πŸ“ (go read her, iykyk)

then the entire entourage:

thirty-four links, zero skips, we ate πŸ’…πŸ”₯

real talk though β€” if you're poking at LPORT map stuff, fm10k_msg_lport_map_pf(9) is right there in the list and it's giving "the other half of this story" 🌈 not claiming anything beyond that, just saying she's listed. go look πŸ‘€

and that's the whole page, bestie β€” short, sweet, and fully documented πŸ§šβ€β™€οΈπŸ’œ

courtesy of that little footer at the bottom: source path starts at ./drivers/net/ethernet/intel/f... (truncated, sad, we don't make the rules 😭) and the date on this beauty is October 2026 πŸ“ so yeah, she's from the future. slay. ⭐

πŸ“¦ where this page comes from