alua_rtpg_queue(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… alua_rtpg_queue(9) β€” the kernel API manual, bestie edition

okay so welcome to alua_rtpg_queue(9), a page from the Kernel API Manual πŸŽ€ yes we're in the kernel API manual today, it's giving very "my code runs in ring 0 and yours doesn't" energy, and honestly? iconic.


✨ NAME ✨

alua_rtpg_queue β€” causes RTPG to be submitted asynchronously, bestie. not now. later. whenever the kernel feels cute. πŸ’«


πŸ¦‹ SYNOPSIS πŸ¦‹

bool alua_rtpg_queue (struct alua_port_group *pg , struct scsi_device
*sdev , struct alua_queue_data *qdata , bool force );

four args, one bool coming back at you. that's the whole vibe check. 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • pg β€” the ALUA port group that's associated with sdev. it's like, sdev's plus-one at the port group party. πŸ’–
  • sdev β€” the SCSI device you want to submit an RTPG for. yes, that one. πŸ‘€
  • qdata β€” info about the callback that gets invoked after the RTPG. like a little note saying "hey, when you're done, do this." πŸ—’οΈβœ¨
  • force β€” whether or not to submit an RTPG if a work item that will submit an RTPG has already been scheduled. no cap, that's literally what it decides. πŸ”₯

🌸 DESCRIPTION 🌸

so the way this works: it returns true if and only if alua_rtpg_work will be called asynchronously. and that function is the one responsible for calling qdata->fn. so like... this function doesn't do the callback. it just makes sure the callback is gonna happen. it's the group-chat organizer, not the person showing up. πŸ’€

big deal energy: true if and only if. the "if and only if" is not a suggestion, it's fr fr a contract. 🧚

⭐ CONTEXT ⭐

may be called from atomic context (alua_check) only if the caller holds an sdev reference. that "only if" is doing a lot of heavy lifting here β€” no reference, no entry. πŸ™ˆ


🌈 SEE ALSO 🌈

  • Kernel file ./drivers/scsi/device_handler/scsi_dh_alua.c β€” go read it, iykyk πŸ‘‘

and that's the page!! πŸ“ if you made it this far you're a real one. this little slice of the kernel API manual came to you from ./drivers/scsi/device_handler, dated October 2026 β€” slay, see you in the source tree bestie πŸ’œπŸ’…πŸŽ€

πŸ“¦ where this page comes from