qed_vf_pf_txq_start(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… qed_vf_pf_txq_start(9)

okay so this one's straight out of the Kernel API Manual, bestie, and it's honestly such a main-character move: your VF just wants to send packets and it can't even start its own TX queue by itself 😭 so it slides a message over to the PF and is like "hey king, start this for me?" πŸŽ€


✨ NAME ✨

qed_vf_pf_txq_start β€” VF side of things, and it does exactly one iconic job: start the TX queue by sending a message to the PF. periodt πŸ’…


🌸 SYNOPSIS 🌸

int qed_vf_pf_txq_start (struct qed_hwfn *p_hwfn , struct qed_queue_cid
*p_cid , dma_addr_t pbl_addr , u16 pbl_size , void __iomem **pp_doorbell
);

πŸ¦‹ ARGUMENTS πŸ¦‹

  • p_hwfn β€” HW device data. literally the hardware handle, your whole vibe check for the device πŸ’–
  • p_cid β€” CID. the queue's little identity card πŸͺͺ
  • pbl_addr β€” PBL address. the address of the PBL, as one does ✨
  • pbl_size β€” PBL Size. how big that PBL is 🌸
  • pp_doorbell β€” pointer to address to which to write the doorbell too. yes, two p's, it's a pointer-to-a-pointer and it points at the spot where you go ding-dong πŸ”” she's giving double-indirection energy
ngl the arg list is short and sweet β€” but don't sleep on pp_doorbell, that's the one you actually need to keep your eyes on πŸ‘€

πŸ”₯ RETURN πŸ”₯

Int. that's it, that's the return. an int. slay πŸ’€


πŸ‘‘ SEE ALSO πŸ‘‘

sibling functions, the whole found family, no cap 🫢


that's the whole page, bestie β€” go start that queue πŸ’–

🌸 mwah 🌸 this lil page lives in ./drivers/net/ethernet/qlogic/qed, dated October 2026, and it's brought to you by the qed_vf_pf_txq_start(9) girlies πŸ§šβ€β™€οΈπŸ’œ

πŸ“¦ where this page comes from