lpfc_nvmet_ls_req(9)

📦 version 7.3.1, in nixpkgs unstable

💅 lpfc_nvmet_ls_req(9) 💅

okay so this is a page from the Kernel API Manual bestie, and it's about lpfc_nvmet_ls_req — literally the function that issues a Link Service request ✨

🌸 NAME 🌸

lpfc_nvmet_ls_req — Issue an Link Service request 🎀 (yes, "an Link Service", the kernel said what it said, we respect the original grammar 💀)

🦋 SYNOPSIS 🦋

int lpfc_nvmet_ls_req (struct nvmet_fc_target_port *targetport , void
*hosthandle , struct nvmefc_ls_req *pnvme_lsreq );

like, it returns an int, and it takes three things. that's the whole vibe check 🫶

✨ ARGUMENTS ✨

  • targetport — pointer to the target instance that's registered with the nvmet transport. it's giving "who am i registered with" energy 👑
  • hosthandle — the hosthandle that the driver set in a prior ls_rqst_rcv. and ngl the driver sets this value to the ndlp pointer, so that's what you're holding fr fr 🎯
  • pnvme_lsreq — the transport nvme_ls_req structure for the LS. this is the actual request package, the main character of the whole operation 💌

💖 DESCRIPTION 💖

so the driver registers this routine to handle any link service request coming from the nvme_fc transport over to a remote nvme-aware port. that's it, that's the job — it's the receptionist at the front desk of your NVMe target 🧚

Return value : 0 - Success, and non-zero means various error codes, in the form of -Exxx 😭 so if you see a negative number, something went sideways, no cap.

🌈 SEE ALSO 🌈

the kernel file lives at ./drivers/scsi/lpfc/lpfc_nvmet.c — go read it if you're obsessed like me 📖

and here's the whole friend group, all of them, every single one 💜:

ok that's the whole page bestie, go forth and handle those link service requests 💅🔥

and that's a wrap 🎀 brought to you by the source directory ./drivers/scsi/lpfc, dated October 2026, and this icon's own name, lpfc_nvmet_ls_req(9) — periodt. 💜✨

📦 where this page comes from