_qed_cxt_acquire_cid(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… _qed_cxt_acquire_cid β€” a Kernel API Manual moment, bestie

okay so picture this: it's giving kernel-internals, it's giving qlogic energy, and the manual it lives in is literally called Kernel API Manual. we're in the 9 section (that's the kernel API section, iykyk), and today's main character is a little function that hands you a fresh cid. let's get into it πŸŽ€


✨ NAME ✨

_qed_cxt_acquire_cid β€” grab yourself a brand new cid of one specific protocol type, for a vf-queue. that's the whole vibe. no cap. πŸ¦‹


🌸 SYNOPSIS 🌸

int _qed_cxt_acquire_cid (struct qed_hwfn *p_hwfn , enum protocol_type
type , u32 *p_cid , u8 vfid );

like, copy it exactly, bestie, don't be creative with the signature πŸ™ˆ


πŸ’– ARGUMENTS πŸ’–

  • p_hwfn β€” the HW device data. this is your hardware handler baddie, the whole device's info lives here πŸ‘‘
  • type β€” the type. yes. that's the description. it's the protocol type, and it's doing the absolute least in the docs but we respect it πŸ’€
  • p_cid β€” a pointer to the cid. you pass in the address, it fills you in. pointer cid, periodt ✨
  • vfid β€” the engine relative index. and here's the important lil detail: it's QED_CXT_PF_CID if it belongs to the PF. write that down πŸ“

πŸ”₯ RETURN πŸ”₯

Int. that's it, that's the return section. an int. slay, honestly. πŸ’…


🧚 SEE ALSO 🧚

first up, the kernel file it lives in β€” go read the source, it's literally right there:

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

and then the whole friend group, in this order:


lowkey the whole cid lifecycle is in that list β€” acquire, release, and the underscore-prefixed twins. read them together, it's giving ✨lore✨

and that's the page, bestie 🫢 this masterpiece comes to you straight from ./drivers/net/ethernet/qlogic/qed, dated October 2026 β€” so go forth and acquire those cids responsibly πŸŒˆβ­πŸ’œ

πŸ“¦ where this page comes from