lpfc_debugfs...eio_trc_data(9)

📦 version 7.3.1, in nixpkgs unstable

okay bestie, welcome to the Kernel API Manual page for lpfc_debugfs...eio_trc_data(9) — yes, the header is giving “dramatic ellipsis,” but the actual function we’re hyping is lpfc_debugfs_nvmeio_trc_data. It’s a kernel API situation, and we’re keeping every single detail intact. 💅

💖 NAME 💖

lpfc_debugfs_nvmeio_trc_data — dump the NVME IO trace list to a buffer. That’s the whole vibe: trace list goes into buffer, slay.

✨ SYNOPSIS ✨

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

🎀 ARGUMENTS 🎀

  • phba — the phba to gather target node info from.
  • buf — the buffer to dump log into.
  • size — the maximum amount of data to process. Respect the limit, bestie.

🦋 DESCRIPTION 🦋

This routine dumps the NVME IO trace associated with phba. That’s it, that’s the routine.

Return Value: this routine returns the amount of bytes that were dumped into buf and will not exceed size. So the byte count is cute, but it knows the limit — no cap.

👀 SEE ALSO 👀

Kernel file ./drivers/scsi/lpfc/lpfc_debugfs.c — yep, that exact path is in the SEE ALSO list, periodt.

xoxo, your ./drivers/scsi/lpfc source/version + October 2026 date + lpfc_debugfs...eio_trc_data(9) title energy 💅✨🫶

📦 where this page comes from