qed_init_pf_wfq(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… qed_init_pf_wfq β€” a Kernel API Manual moment (section 9, bestie)

Okay so picture this: you're deep in the kernel API manual, section 9, and you stumble onto qed_init_pf_wfq. That's the whole vibe. This little icon does exactly one thing and does it slay: it initializes the WFQ weight of the specified PF. That's it. That's the function. πŸŽ€


✨ SYNOPSIS ✨

int qed_init_pf_wfq (struct qed_hwfn *p_hwfn , struct qed_ptt *p_ptt ,
u8 pf_id , u16 pf_wfq );

No cap, that's the signature, copied character for character because I respect you. 🫢


🌸 ARGUMENTS 🌸

  • p_hwfn β€” the HW device data. Like, the whole hardware situation, wrapped up in a struct. Main character energy honestly.
  • p_ptt β€” the Ptt window used for writing the registers. That's your little doorway into register-land, iykyk. πŸšͺ✨
  • pf_id β€” the PF ID. Which PF? This one. πŸ’…
  • pf_wfq β€” the WFQ weight. Must be non-zero. Not "should be", not "ideally" β€” must. Zero is not invited to this party. πŸ™ˆ

⭐ RETURN ⭐

  • 0 on success β€” slay, you ate, periodt. πŸ‘‘
  • -1 on error β€” it's giving struggle, but at least it's honest. 😭

πŸ¦‹ SEE ALSO πŸ¦‹

Bestie, the lore goes deep. First up, the kernel file:

./drivers/net/ethernet/qlogic/qed/qed_hsi.h

And the whole friend group:

That's a whole group chat, lowkey. Go read them, they're all interconnected and it's honestly iconic. 🌈


🫢 Real talk though: pf_wfq being non-zero isn't a suggestion, it's a requirement. Respect the constraint, bestie. πŸ’–

And that's the page! Huge shoutout to the source/version <cyan>./drivers/net/ethernet/qlogic/qed</cyan> and the date <purple>October 2026</purple> β€” this manual entry <hotpink>qed_init_pf_wfq(9)</hotpink> was brought to you by them, and honestly? They ate. πŸ“βœ¨ Byeee, go initialize some weights! πŸ§šπŸ’œ

πŸ“¦ where this page comes from