lpfc_sli_ringpostbuf_get(9)

📦 version 7.3.1, in nixpkgs unstable

💅 NAME 💅

okay bestie, welcome to lpfc_sli_ringpostbuf_get(9) from the Kernel API Manual — the function that searches buffers for unsolicited CT and ELS events. It’s giving “where’s my buffer at” energy, but make it kernel. 💖

✨ SYNOPSIS ✨

struct lpfc_dmabuf * lpfc_sli_ringpostbuf_get (struct lpfc_hba *phba ,
       struct lpfc_sli_ring *pring , dma_addr_t phys );

🎀 ARGUMENTS 🎀

  • phba — pointer to the HBA context object. That’s the HBA’s whole context situation, bestie.
  • pring — pointer to the driver SLI ring object. The ring in question, no cap.
  • phys — DMA address of the buffer. Literally the DMA address, exactly as advertised. 🦋

🦋 DESCRIPTION 🦋

So here’s the vibe: this function searches the buffer list using the dma_address of the unsolicited event to find the driver’s lpfc_dmabuf object that corresponds to that dma_address. It’s a whole “match the address to the buffer” moment, and honestly? iconic.

It returns the lpfc_dmabuf object if a buffer is found; otherwise it returns NULL. That’s the whole yes/no of it, periodt. 💅

This function is called by the ct and els unsolicited event handlers to get the buffer associated with the unsolicited event. They’re the ones sliding into its DMs for the buffer, iykyk.

Heads up, bestie: this function is called with no lock held. Not even a tiny one. 🔥

🌈 SEE ALSO 🌈

The kernel file is ./drivers/scsi/lpfc/lpfc_sli.c. The whole friend group in SEE ALSO — no gatekeeping, every single one — is:

mwah 💖 cute little sign-off: this page comes from source/version ./drivers/scsi/lpfc, dated October 2026, and you absolutely ate that read, bestie. 🎀✨

📦 where this page comes from