lpfc_els_rcv_farpr(9)

📦 version 7.3.1, in nixpkgs unstable

💅 lpfc_els_rcv_farpr — a kernel API manual moment (yes, from the 9 section, bestie)

okay so picture this: you're deep in the Kernel API Manual, section 9, and you've stumbled onto lpfc_els_rcv_farpr. Cute name, right? It's giving "the FC person at the party who handles the address-resolution small talk." Let's get into it 🫶

✨ NAME ✨

lpfc_els_rcv_farpr — literally just: process an unsolicited farp response iocb. that's the whole vibe. 🌸

🦋 SYNOPSIS 🦋

int lpfc_els_rcv_farpr (struct lpfc_vport *vport , struct lpfc_iocbq
*cmdiocb , struct lpfc_nodelist *ndlp );

three pointers walk into a function and return an int. iconic behavior honestly 💅

🎀 ARGUMENTS 🎀

  • vport — pointer to a host virtual N_Port data structure. the vport in question 👑
  • cmdiocb — pointer to lpfc command iocb data structure. the command iocb, arriving with receipts.
  • ndlp — pointer to a node-list data structure. the node-list entry, keeping it all together 🌈

💖 DESCRIPTION 💖

so this routine processes a Fibre Channel Address Resolution Protocol Response (FARPR) IOCB that showed up as an ELS unsolicited event. and what does it do with it? it simply invokes the lpfc_els_rsp_acc routine to the remote node, to accept the FARP response request. that's it. that's the function. lowkey elegant, no cap ✨

Return code 0 — Successfully processed FARPR IOCB (currently always return 0). yes bestie, always. it's a 0 machine fr fr 😭

🌟 SEE ALSO 🌟

Kernel file ./drivers/scsi/lpfc/lpfc_els.c — plus the entire extended friendship group of functions, and we're listing every single one because nobody gets left on read 💜

and that's the whole page, bestie — no notes, no cap 💅✨

this masterpiece lives in ./drivers/scsi/lpfc, dated October 2026, and it's filed under lpfc_els_rcv_farpr(9). go forth and accept those FARP responses. slay 🎀🦋💖

📦 where this page comes from