fnic_fcoe_pr...s_flogi_resp(9)
πΈ fnic_fcoe_process_flogi_resp πΈ
okay so bestie, this is a page from the Kernel API Manual β yes, the kernel manual, we're doing big-girl kernel hours π
β and it's all about one lil function called fnic_fcoe_process_flogi_resp. Buckle up, it's short and sweet.
β¨ NAME β¨
fnic_fcoe_process_flogi_resp β literally the function that processes the FLOGI response from the FCF. that's it, that's the whole job π«Ά
π¦ SYNOPSIS π¦
void fnic_fcoe_process_flogi_resp (struct fnic *fnic , struct fip_header
*fiph );
no return value, she just does things. void queen π
π ARGUMENTS π
fnicβ Handle to the fnic driver instance. like, the actual driver vibe, the main character of this whole situation πfiphβ Received frame. the frame that showed up. the mail, if you will π
π DESCRIPTION π
okay so here's the tea β β if it's successful, she saves the assigned fc_id and MAC, programs the firmware, and starts fdls discovery. iconic behaviour, no notes β¨
but if it's not successful? she restarts vlan discovery instead. different path, same determination πͺ not me being emotionally invested in a FLOGI response π
π SEE ALSO π
Kernel file ./drivers/scsi/fnic/fip.c, plus the whole friend group β go say hi:
fnic_fcoe_reset_vlans(9)fnic_fcoe_send_vlan_req(9)fnic_fcoe_process_vlan_resp(9)fnic_fcoe_start_fcf_discovery(9)fnic_fcoe_fip_discovery_resp(9)fnic_fcoe_start_flogi(9)fnic_common_fip_cleanup(9)fnic_fcoe_process_cvl(9)fdls_fip_recv_frame(9)fnic_handle_fip_timer(9)fnic_handle_enode_ka_timer(9)fnic_handle_vn_ka_timer(9)fnic_vlan_discovery_timeout(9)fnic_work_on_fcs_ka_timer(9)fnic_handle_fcs_ka_timer(9)
mwah π this page lives in ./drivers/scsi/fnic and it's dated October 2026 β future-coded of her, honestly. stay slay, stay discovered, periodt π§ββοΈ
π¦ 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