fc_exch_pool_reset(9)

📦 version 7.3.1, in nixpkgs unstable

💅 fc_exch_pool_reset — Reset a per cpu exchange pool 🎀

okay so bestie, we're deep in the Kernel API Manual today (yes, the Kernel API Manual, section 9, we're fancy like that ✨) and the star of the show is fc_exch_pool_reset. it's a reset. for an exchange pool. per cpu. iykyk 💖

🌈 SYNOPSIS

void fc_exch_pool_reset (struct fc_lport *lport , struct fc_exch_pool
*pool , u32 sid , u32 did );

that's it. that's the whole call. no return value, it's giving void and unbothered 💅

🫶 ARGUMENTS

  • lport — the local port that the exchange pool lives on. like, whose pool even is this 🎀
  • pool — the actual exchange pool you're resetting. the main character of this function fr
  • sid — the source ID 👀
  • did — the destination ID 👑

💖 DESCRIPTION

okay so here's the tea ☕: fc_exch_pool_reset resets a per cpu exches pool — yes it says "exches", that's the manpage's own spelling, i'm not touching it — and it releases all of its sequences and exchanges. literally all of them. gone. released. slay 💀

but wait, there's a filter moment ✨:

  • if sid is non-zero, then it resets only exchanges that we sourced from the local port's FID 🐝
  • if did is non-zero, then it only resets exchanges destined for the local port's FID 🎯

so like, pass zeros if you want the whole pool reset, or pass real IDs if you wanna be picky. either way, it's a reset, and it ate 🔥

👑 SEE ALSO

bestie, buckle up, this list is long and honestly iconic for it 🌸 it all comes from the kernel file ./drivers/scsi/libfc/fc_exch.c:

like i said. a lot. every single one of them, no cap 🧚

ngl there's no RETURN VALUE and no ERRORS section here, because it returns void and it simply does the thing. that's main character energy fr fr 🌟

and that's the whole vibe check bestie 🦋 this little gem lives in ./drivers/scsi/libfc and the version stamp says October 2026 — so yeah, future-timestamped and still slaying 💜 go reset a pool, you've got this 🫶✨

📦 where this page comes from