lpfc_find_cpu_handle(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

Okay bestie, welcome to lpfc_find_cpu_handle(9) β€” yes, that’s the page name, and it’s part of the Kernel API Manual. Not me being obsessed with a CPU matcher, but the NAME says it all: Find the CPU that corresponds to the specified Queue. It’s giving utility function with main character energy. πŸ’…

✨ SYNOPSIS ✨

uint16_t lpfc_find_cpu_handle (struct lpfc_hba *phba , uint16_t id , int
       match );

Lowkey just the signature, but make it make sense: uint16_t is the return type, and the function takes phba, id, and match. Slay. ✨

πŸ¦‹ ARGUMENTS πŸ¦‹

  • phba β€” pointer to lpfc hba data structure. Like, the HBA’s main character pointer. 🫢
  • id β€” EQ vector index or Hardware Queue index. iykyk.
  • match β€” LPFC_FIND_BY_EQ = match by EQ, and LPFC_FIND_BY_HDWQ = match by Hardware Queue. Return the CPU that matches the selection criteria. The way this selector ate and left no crumbs. πŸ’–

🌈 SEE ALSO 🌈

Kernel file: ./drivers/scsi/lpfc/lpfc_init.c β€” that’s the home base. Then here’s the whole group chat of cross-refs, fr fr:


Okay bestie, that’s the whole lpfc_find_cpu_handle(9) page β€” source/version spot is ./drivers/scsi/lpfc, dated October 2026, and the manual name is still lpfc_find_cpu_handle(9). Go find your CPU and slay, periodt. πŸ’…βœ¨πŸ¦‹

πŸ“¦ where this page comes from