fc_vport_sched_delete(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

ok so bestie, this is fc_vport_sched_delete(9) β€” the kernel API manual page for it, and honestly? it does exactly one thing and it does it iconically: it's the workq-based delete request for a vport. that's it. that's the whole vibe. a vport needs to go, and this function schedules the deletion through the workqueue so the actual teardown happens later in work-context instead of, like, right now. lowkey elegant. ✨


πŸŽ€ SYNOPSIS πŸŽ€

void fc_vport_sched_delete (struct work_struct *work );

no return value, no drama β€” she's void, she returns nothing, she just does. 🫢


🌸 ARGUMENTS 🌸

  • work β€” the vport to be deleted. yes, it comes in as a struct work_struct * because workqueue things are built different β€” that struct is how the workqueue knows what to pick up and run. πŸ¦‹

🧚 SEE ALSO 🧚

like, the whole FC transport friend group is here, and we're tagging everyone in the group chat, no cap:

and the actual source file (the main character's address, iykyk): Kernel file ./drivers/scsi/scsi_transport_fc.c πŸ’–


okay that's the whole page, bestie β€” go schedule that delete πŸ’…βœ¨

this little cutie lives under ./drivers/scsi (that's the source/version corner of the page 🌈) and it's dated October 2026 β€” so yeah, mark your calendar, she's from the future πŸŽ€πŸ’–πŸ«Ά

πŸ“¦ where this page comes from