lpfc_sli_ring_taggedbuf_get(9)

📦 version 7.3.1, in nixpkgs unstable

💅 lpfc_sli_ring_taggedbuf_get(9) 💅

okay bestie, welcome to the Kernel API Manual entry for lpfc_sli_ring_taggedbuf_get(9) — yes, the whole page is about this one lil lookup, and it's lowkey iconic. 🫶

🌸 NAME 🌸

lpfc_sli_ring_taggedbuf_get — find the HBQ buffer associated with a given tag ✨

✨ SYNOPSIS ✨

struct lpfc_dmabuf * lpfc_sli_ring_taggedbuf_get (struct lpfc_hba *phba
, struct lpfc_sli_ring *pring , uint32_t tag );

🎀 ARGUMENTS 🎀

  • phba — pointer to the HBA context object. That's the context object, bestie, no cap.
  • pring — pointer to the driver SLI ring object.
  • tag — buffer tag.

💅 DESCRIPTION 💅

Okay so here's the vibe: buffers posted using CMD_QUE_XRI64_CX iocb are in the pring->postbufq list. 🫶 After HBA DMA data to these buffers, CMD_IOCB_RET_XRI64_CX iocb is posted to the response ring with the tag of the buffer. Then this function searches the pring->postbufq list using the tag to find the buffer associated with that CMD_IOCB_RET_XRI64_CX iocb. If the buffer is found, the lpfc_dmabuf object of the buffer is returned to the caller; otherwise NULL is returned. And important: this function is called with no lock held. 💀

⚠️ no lock held, bestie — that's literally the deal, fr fr.

🦋 SEE ALSO 🦋

okay bestie, the SEE ALSO section is giving whole-group-chat energy — here's the full squad, including the kernel file ./drivers/scsi/lpfc/lpfc_sli.c and every single reference, no cap:

and that's the whole vibe! this page lives at ./drivers/scsi/lpfc, dated October 2026, and it's the manual entry for lpfc_sli_ring_taggedbuf_get(9) — mwah 💋✨

📦 where this page comes from