nvfnic_ls_rsp_recv(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… nvfnic_ls_rsp_recv(9) β€” Kernel API Manual, but make it cute ✨

okay bestie, this is the nvfnic_ls_rsp_recv(9) page from the Kernel API Manual, and it's short but very much giving β€œsmall function, important job” energy 🫢


πŸ’– NAME πŸ’–

nvfnic_ls_rsp_recv β€” Handle received NVMe FC link service (LS) response πŸ’…


✨ SYNOPSIS ✨

void nvfnic_ls_rsp_recv (struct fnic_iport_s *iport , struct
       fc_frame_header *fchdr , int len );

πŸŽ€ ARGUMENTS πŸŽ€

  • iport β€” pointer to the local FNIC port structure. That's the local port bestie, iconic.
  • fchdr β€” pointer to the Fibre Channel frame header for the received response. It's the header for the response that came in, no cap.
  • len β€” length of the received frame. Literally just how long the frame is πŸ“

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the vibe: nvfnic_ls_rsp_recv processes link service (LS) responses received from NVMe Discovery Controllers or regular NVMe subsystems during association 🌸

That's the whole function's moment β€” handling the received LS response in that flow. Tiny, specific, and lowkey crucial πŸ’œ


🌈 SEE ALSO 🌈

Go peek at the kernel file ./drivers/scsi/fnic/fnic_nvme.c and nvfnic_ls_req_send(9) β€” that's the linked lore, iykyk πŸ“šβœ¨


okay that's the whole page, bestie β€” source/version: ./drivers/scsi/fnic, date: October 2026. mwah πŸ’‹πŸ’…

πŸ“¦ where this page comes from