lpfc_sli4_nvmet_alloc(9)
π lpfc_sli4_nvmet_alloc
okay so bestie, welcome to the Kernel API Manual β¨ β this one's a little function from the SCSI lpfc driver and honestly it's giving "small but mighty" energy. Let's get into it π
πΈ NAME πΈ
lpfc_sli4_nvmet_alloc β allocates an SLI4 Receive buffer π«Ά
π¦ SYNOPSIS π¦
struct rqb_dmabuf * lpfc_sli4_nvmet_alloc (struct lpfc_hba *phba );
π ARGUMENTS π
phbaβ the HBA you're allocating a receive buffer for, like, that's the whole vibe check right there π
β DESCRIPTION β
So what does it actually do? It allocates a DMA-mapped receive buffer straight out of the lpfc_hrb_pool PCI pool β and it also grabs a non-DMA-mapped container to go with it π§β¨ that's it, that's the whole job, and it does it flawlessly, no cap.
π₯ RETURN π₯
- pointer to HBQ on success π
NULLon failure π (sad but honest)
π SEE ALSO π
Kernel file ./drivers/scsi/lpfc/lpfc_mem.c, plus the whole friend group:
lpfc_mem_alloc(9)lpfc_mem_free(9)lpfc_mem_free_all(9)lpfc_mbuf_alloc(9)__lpfc_mbuf_free(9)lpfc_mbuf_free(9)lpfc_nvmet_buf_alloc(9)lpfc_nvmet_buf_free(9)lpfc_els_hbq_alloc(9)lpfc_els_hbq_free(9)lpfc_sli4_rb_alloc(9)lpfc_sli4_rb_free(9)lpfc_sli4_nvmet_free(9)lpfc_in_buf_free(9)lpfc_rq_buf_free(9)
ngl, if you're poking around in ./drivers/scsi/lpfc you're lowkey built different π
and that's the tea, bestie π this page came to you courtesy of the source tree at ./drivers/scsi/lpfc, dated October 2026 β periodt, go forth and allocate responsibly π
β¨π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms