lpfc_nvme_delete_queue(9)
π lpfc_nvme_delete_queue(9) π
okay bestie, welcome to the Kernel API Manual page for lpfc_nvme_delete_queue(9) β yes that's the whole manual name, and yes we're gonna get through it together π«Ά
β¨ NAME β¨
lpfc_nvme_delete_queue β
and that's it. That's the whole name section. no description, no little dash-explainer, nothing. the manpage literally just left us on read π the way that the NAME field is empty is giving "submitted assignment with the title filled in and nothing else" ngl.
πΈ SYNOPSIS πΈ
void lpfc_nvme_delete_queue (struct nvme_fc_local_port *pnvme_lport ,
unsigned int qidx , void *handle );
three args, no return type but void (so, no return value coming back to you, babe π
). note the spaces before those commas β yes they're in the original, yes we're keeping them, that's just how it's written and we respect it.
π ARGUMENTS π
pnvme_lportβ the transport localport that LS is to be issued from. like, this is where it all happens πqidxβ a cpu index used to affinitize IO queues and MSIX vectors. so it's the little number tying your queue to a specific cpu, iykyk π₯handleβ an opaque driver handle fromlpfc_nvme_create_queue. "opaque" meaning don't peek inside, just pass it along like a sealed note π¦
π¦ DESCRIPTION π¦
okay so here's the actual tea: the driver registers this routine to free any internal data structures that bind the qidx to its internal IO queues. that's the whole job. cleanup duty. the un-glamorous but absolutely essential part of the group project β¨
and then, the return value situation:
Return value : 0 - Success TODO: What are the failure codes.
so 0 means success β
... and the failure codes are literally a TODO. as in, not documented yet. as in, the author left it as a note to future self and future self said "nah" π so if you were hoping for a full list of what can go wrong β bestie, same. it's not there. don't invent it, don't guess it, just know that 0 = success and the rest is a mystery π§
π SEE ALSO π
the kernel file lives at ./drivers/scsi/lpfc/lpfc_nvme.c π and here's the whole squad of related functions, all in (9):
lpfc_nvme_create_queue(9)β the one that made the handle you're passing in, the yin to this yanglpfc_nvme_handle_lsreq(9)__lpfc_nvme_ls_req_cmp(9)__lpfc_nvme_ls_req(9)lpfc_nvme_ls_req(9)__lpfc_nvme_ls_abort(9)lpfc_nvme_ls_abort(9)lpfc_nvme_prep_io_cmd(9)lpfc_nvme_prep_io_dma(9)lpfc_nvme_fcp_io_submit(9)lpfc_nvme_abort_fcreq_cmpl(9)lpfc_nvme_fcp_abort(9)lpfc_release_nvme_buf(9)lpfc_nvme_create_localport(9)lpfc_nvme_destroy_localport(9)lpfc_sli4_nvme_pci_offline_aborted(9)lpfc_sli4_nvme_xri_aborted(9)lpfc_nvme_wait_for_io_drain(9)lpfc_nvme_flush_abts_list(9)lpfc_nvmels_flush_cmd(9)
that's twenty entries, count 'em, we did not skip a single one π go read them, they're all right there in the same file, it's giving family reunion π
and that's a wrap, bestie!! π this page is brought to you by version/source ./drivers/scsi/lpfc, dated October 2026 β iconic, timeless, slightly mysterious, just like that missing failure-code list π
π see u in the next manpage, mwah π«Ά
π¦ 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