fc_seq_alloc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

okay so bestie, this is the fc_seq_alloc(9) page from the Kernel API Manual ✨ β€” allocate a sequence for a given exchange, and the title is literally the function we’re talking about. No cap. πŸ’…


✨ SYNOPSIS ✨

here’s the exact signature, character for character, because we do not play with code 🫢:

struct fc_seq * fc_seq_alloc (struct fc_exch *ep , u8 seq_id );

🫢 ARGUMENTS 🫢

  • ep β€” the exchange to allocate a new sequence for πŸ’–
  • seq_id β€” the sequence ID to be used ✨

πŸ’… DESCRIPTION πŸ’…

The way this works: multiple originated sequences on the same exchange? not supported, bestie. So if this exchange already had an originated sequence, that sequence is complete, and we reallocate the same sequence. That’s the whole tea β˜• β€” no extra originated sequences stacked on the same exchange, and the previous one is already complete, fr fr.

lowkey important: no multiple originated sequences on the same exchange, periodt. Any previously originated sequence on this exchange is complete, and we reallocate the same sequence. πŸ’€

🌈 SEE ALSO 🌈

the whole see-also squad, in the exact order, no cap πŸ’…:

🫢 source/version: ./drivers/scsi/libfc; date: October 2026. That’s the whole page, bestie β€” mwah πŸ’–

πŸ“¦ where this page comes from