lpfc_used_vpi_show(9)

📦 version 7.3.1, in nixpkgs unstable

💅 lpfc_used_vpi_show(9) — Kernel API Manual ✨

okay so bestie, this is a page straight out of the Kernel API Manual and it's lowkey iconic — it's all about lpfc_used_vpi_show, which returns the max vpi minus the available vpi. math queen behavior honestly 🎀

🌸 NAME 🌸

lpfc_used_vpi_show — Return maximum vpi minus the available vpi 💖

✨ SYNOPSIS ✨

ssize_t lpfc_used_vpi_show (struct device *dev , struct device_attribute
*attr , char *buf );

🦋 ARGUMENTS 🦋

  • dev — the class device that gets converted into a Scsi_host. it's giving main character energy, literally the whole point of the call 🫶
  • attr — the device attribute. not used. she's just there for the vibe check, no cap 💅
  • buf — on return this contains the used vpi count in decimal, or the string "Unknown". so either a cute little number or a mystery 🙈

🌈 DESCRIPTION 🌈

So what actually happens? It calls lpfc_get_hba_info asking for just the mvpi and avpi counts — that's it, that's the whole ask, keep it focused bestie ⭐

Here's the plot twist though: if lpfc_get_hba_info returns zero (that's a failure), the buffer text gets set to "Unknown" and the buffer length is returned. so yeah 😭 the caller must check for "Unknown" in the buffer to detect a failure. don't skip that check, i'm literally begging 🫶

Lowkey important: the failure signal lives inside the buffer, not in the return value. check your buffer, bestie. periodt. 💀

👑 RETURN 👑

size of formatted string. that's the return value, slay ✨

🧚 SEE ALSO 🧚

Kernel file ./drivers/scsi/lpfc/lpfc_attr.c

and that's the whole page, bestie — go forth and check that buffer for "Unknown" 💜

mwah 💋 this came from the kernel source tree at ./drivers/scsi/lpfc, version vibes dated October 2026 — catch you in the next manpage, ily 🎀✨

📦 where this page comes from