lpfc_debugf...ripools_data(9)

👑 lpfc_debugf...ripools_data(9) — the Kernel API Manual, bestie edition ✨

okay so real talk, this is a page from the Kernel API Manual, and the function we're hyping up today is lpfc_debugfs_multixripools_data(9). yes the title is abbreviated with ... because apparently even the kernel needs to keep it cute and short 💅. anyway. sit down, grab a strawberry 🍓, let's get into it.

---

✨ NAME ✨

lpfc_debugfs_multixripools_data — Display multi-XRI pools information 🎀

like. that's the whole vibe. it shows you your multi-XRI pool tea.

---

🦋 SYNOPSIS 🦋

int lpfc_debugfs_multixripools_data (struct lpfc_hba *phba , char *buf ,
int size );

not me formatting this exactly how the page does it, i'm nothing if not faithful to the source 😭. keep it verbatim, bestie, don't touch.

---

🌸 ARGUMENTS 🌸

three lil besties walk into a function:

• phba — The HBA to gather host buffer info from. like, this is the card, the main character of the operation 👑. everything gets read off this one.
• buf — The buffer to dump log into. this is the lil container where the output goes to live its life. fill it up, queen.
• size — The maximum amount of data to process. the hard cap, the limit, the "know your lane" number 🙈. do not exceed.

---

💖 DESCRIPTION 💖

so what does this thing actually do? it displays current multi-XRI pools information, and yes that includes the XRI count in public, private and txcmplq. all three. it's giving full transparency. it also shows you the current high and low watermark — the way that it tracks both ends of the range is honestly iconic 🌈.

Return Value: this routine returns the amount of bytes that were dumped into buf, and no cap it will not exceed size. boundaries! we love boundaries! 🫶

---

⭐ SEE ALSO ⭐

okay this next part is long, but i'm not skipping a single one, because every reference here is family 💜. first up, the actual file — it lives right here:

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

and now the whole group chat of related pages, in exactly the order the manual gives them:

• lpfc_debugfs_disc_trc_data(9)
• lpfc_debugfs_slow_ring_trc_data(9)
• lpfc_debugfs_hbqinfo_data(9)
• lpfc_debugfs_commonxripools_data(9)
• lpfc_debugfs_lockstat_data(9)
• lpfc_debugfs_dumpHBASlim_data(9)
• lpfc_debugfs_dumpHostSlim_data(9)
• lpfc_debugfs_nodelist_data(9)
• lpfc_debugfs_nvmestat_data(9)
• lpfc_debugfs_scsistat_data(9)
• lpfc_debugfs_ioktime_data(9)
• lpfc_debugfs_nvmeio_trc_data(9)
• lpfc_debugfs_hdwqstat_data(9)
• lpfc_debugfs_disc_trc(9)
• lpfc_debugfs_slow_ring_trc(9)
• lpfc_debugfs_nvme_trc(9)
• lpfc_debugfs_disc_trc_open(9)
• lpfc_debugfs_slow_ring_trc_open(9)
• lpfc_debugfs_hbqinfo_open(9)
• lpfc_debugfs_multixripools_open(9)
• lpfc_debugfs_lockstat_open(9)
• lpfc_debugfs_ras_log_open(9)
• lpfc_debugfs_dumpHBASlim_open(9)
• lpfc_debugfs_dumpHostSlim_open(9)
• lpfc_debugfs_nodelist_open(9)
• lpfc_debugfs_lseek(9)
• lpfc_debugfs_read(9)
• lpfc_debugfs_release(9)
• lpfc_debugfs_multixripools_write(9)
• lpfc_idiag_cmd_get(9)
• lpfc_idiag_open(9)
• lpfc_idiag_release(9)
• lpfc_idiag_cmd_release(9)
• lpfc_idiag_pcicfg_read(9)
• lpfc_idiag_pcicfg_write(9)
• lpfc_idiag_baracc_read(9)
• lpfc_idiag_baracc_write(9)
• lpfc_idiag_queinfo_read(9)
• lpfc_idiag_que_param_check(9)
• lpfc_idiag_queacc_read_qe(9)
• lpfc_idiag_queacc_read(9)
• lpfc_idiag_queacc_write(9)
• lpfc_idiag_drbacc_read_reg(9)
• lpfc_idiag_drbacc_read(9)
• lpfc_idiag_drbacc_write(9)
• lpfc_idiag_ctlacc_read_reg(9)
• lpfc_idiag_ctlacc_read(9)
• lpfc_idiag_ctlacc_write(9)
• lpfc_idiag_mbxacc_get_setup(9)
• lpfc_idiag_mbxacc_read(9)
• lpfc_idiag_mbxacc_write(9)
• lpfc_idiag_extacc_avail_get(9)
• lpfc_idiag_extacc_alloc_get(9)
• lpfc_idiag_extacc_drivr_get(9)
• lpfc_idiag_extacc_write(9)
• lpfc_idiag_extacc_read(9)
• lpfc_debugfs_initialize(9)
• lpfc_debugfs_terminate(9)
• lpfc_debug_dump_all_queues(9)

that's the whole roster. no cap, i listed every single one 🫡💀

---

and that's the page, bestie. go read your XRI pools. slay. 💅

sign-off time 🎀 — this whole thing is filed under ./drivers/scsi/lpfc, dated October 2026, and yes the header/footer both say lpfc_debugf...ripools_data(9) because the terminal just couldn't handle her full name. periodt. ✨🦋💖