lpfc_sli4_c...pool_destroy(9)

📦 version 7.3.1, in nixpkgs unstable

💅 lpfc_sli4_c...pool_destroy(9) — straight outta the Kernel API Manual ✨

okay bestie, buckle up 🎀 this one's a little function with a big job, and yes the title is lowkey truncated in the header (that's just how the page rolls, lpfc_sli4_c...pool_destroy(9)), but we're gonna learn it properly. no cap. 🌸

🦋 NAME

lpfc_sli4_cq_event_pool_destroy — Free completion-queue event free pool 💖

✨ SYNOPSIS

void lpfc_sli4_cq_event_pool_destroy (struct lpfc_hba *phba );

🎀 ARGUMENTS

  • phba — pointer to the lpfc hba data structure. that's the whole personality of the argument list, she's lowkey mysterious but she's carrying the entire hba 🫶

👑 DESCRIPTION

okay so picture this: this routine is invoked to free the pool of completion queue events — and when does that happen? at driver unload time, periodt. 💅 that's her whole moment.

but here's the part where you need to pay attention, bestie, because this is a responsibility type of situation and not the fun kind 😭 — it is the responsibility of the driver cleanup routine to free all the outstanding completion-queue events allocated from this pool back into the pool before invoking this routine to destroy the pool. like, the pool has to be empty-ish first. you can't just nuke the pool and leave the events floating, that's not the vibe. 🚩

fr fr: drain your outstanding events back into the pool first, then call this to destroy the pool. that's the order of operations, iykyk. 🧚

🌈 SEE ALSO

she has a lot of friends, and we are NOT leaving anybody out of the list, so here's the whole crew 💜 — starting with the kernel file herself:

and that's the whole page, bestie, we ate that 💅✨ this lil number lives over in ./drivers/scsi/lpfc and she's stamped October 2026 — iconic, no notes, mwah 🎀🦋💖

📦 where this page comes from