lpfc_handle_rrq_active(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

okay bestie, welcome to the Kernel API Manual entry for lpfc_handle_rrq_active πŸ’…

lpfc_handle_rrq_active β€” Checks if RRQ has waithed RATOV.

yes the "waithed" is staying, it's part of the lore now, we don't touch it 🫢

✨ SYNOPSIS ✨

void lpfc_handle_rrq_active (struct lpfc_hba *phba );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • phba β€” Pointer to HBA context object. it's giving "the whole entire world lives in here" energy, lowkey πŸ‘‘

πŸ’– DESCRIPTION πŸ’–

so picture this: this function gets called with hbalock held, right? like the lock is already in your hand, do not grab it again, that's not the vibe πŸ™ˆ

then it does a lil vibe check β€” has stop_time been reached? (ratov, from when we set rrq active). if the answer is yes and the send_rrq flag is set, it's go time and it calls lpfc_send_rrq πŸ”₯

but if the send_rrq flag is not set? then it just calls the routine to clear the rrq and free the rrq resource. no send, just cleanup, we love a tidy queen 🧹✨

and before dipping out of the routine, the timer gets set to the next rrq that's going to expire β€” so nothing gets left hanging, periodt β°πŸ’œ


🌈 SEE ALSO 🌈

main character file: Kernel file ./drivers/scsi/lpfc/lpfc_sli.c β€” and honestly the whole friend group showed up, look at this roster πŸ˜­πŸ’–


and that's the whole page bestie, go clear those rrqs responsibly πŸ’œ this one came straight outta ./drivers/scsi/lpfc, dated October 2026, and it's the lpfc_handle_rrq_active(9) girl herself signing off βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from