lpfc_rampdown_queue_depth(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… lpfc_rampdown_queue_depth

okay so bestie, welcome to the Kernel API Manual, section 9 β€” this one is lpfc_rampdown_queue_depth, and it's giving β€œemergency queue chill-out button” energy. ✨

🌸 NAME 🌸

lpfc_rampdown_queue_depth β€” post RAMP_DOWN_QUEUE event to worker thread. πŸ’–

✨ SYNOPSIS ✨

void lpfc_rampdown_queue_depth (struct lpfc_hba *phba );

πŸŽ€ ARGUMENTS πŸŽ€

  • phba β€” The Hba for which this call is being executed. That's the struct lpfc_hba *, bestie β€” the HBA whose business we're handling. 🫢

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so this routine gets called when there's a resource error in the driver or firmware. It posts a WORKER_RAMP_DOWN_QUEUE event for phba. It posts at most 1 event each second β€” yes, it's rate-limited, we love a calm queen. πŸ‘‘

It also wakes up the worker thread of phba to process the WORKER_RAM_DOWN_EVENT event. And yes, the description literally says WORKER_RAM_DOWN_EVENT there β€” we are keeping it exactly as written, no editing the source vibes. πŸ’€

🚨 No lock held, bestie. This routine should be called with no lock held. Do not be the person holding a lock here, okay? 😭

🌈 SEE ALSO 🌈

The kernel file in question:

  • ./drivers/scsi/lpfc/lpfc_scsi.c

And here's the full squad of related kernel API pages β€” every single one, no cap:


okay that's the whole page, bestie. πŸ’– This source lives at ./drivers/scsi/lpfc, and this edition is dated October 2026 β€” from the Kernel API Manual, section 9. Slay, go forth, and don't hold that lock. πŸ’…βœ¨

πŸ“¦ where this page comes from