fcoe_ctlr_vn_disc(9)
π fcoe_ctlr_vn_disc(9) β the Kernel API Manual glow-up π
okay bestie, so this is a page from the Kernel API Manual (yes, section 9, the ~fancy~ kernel-internal section), and the star of the show is fcoe_ctlr_vn_disc. she's a tiny function with one job and she does it. let's get into it β¨
β¨ NAME β¨
fcoe_ctlr_vn_disc β report FIP VN_port discovery results after claim state.
like, she's the one who comes back from the group chat and tells everyone who's actually in the group. the receipts girlie of FIP VN_port discovery π
πΈ SYNOPSIS πΈ
void fcoe_ctlr_vn_disc (struct fcoe_ctlr *fip );
yeah that's it. one argument, returns void, no drama, no return value, no cap π«Ά
π¦ ARGUMENTS π¦
fipβ the FCoE controller. that's your whole entire main character of this story, honestly. she's thestruct fcoe_ctlr *and everything happens through her π₯
π§ DESCRIPTION π§
so here's the vibe: fcoe_ctlr_vn_disc starts the FLOGI and PLOGI login process to each discovered rport for which we've received at least one beacon. one beacon minimum, bestie β we are not doing zero-beacon situations, that's not the move π
and then, the moment of truth: it performs the discovery complete callback. so like. she finishes the discovery and she announces it. the callback is the "we're so back" post π
tbh she's doing the closing ceremony of the claim state β reporting the discovery results like a good little narrator π
π SEE ALSO π
if you wanna go down the rabbit hole (and you do, iykyk), the page points you at the kernel file ./drivers/scsi/fcoe/fcoe_ctlr.c plus this whole extended universe of siblings:
fcoe_ctlr_set_state(9)fcoe_ctlr_mtu_valid(9)fcoe_ctlr_fcf_usable(9)fcoe_ctlr_map_dest(9)fcoe_ctlr_init(9)fcoe_sysfs_fcf_add(9)fcoe_sysfs_fcf_del(9)fcoe_ctlr_reset_fcfs(9)fcoe_ctlr_destroy(9)fcoe_ctlr_announce(9)fcoe_ctlr_fcoe_size(9)fcoe_ctlr_solicit(9)fcoe_ctlr_link_up(9)fcoe_ctlr_reset(9)fcoe_ctlr_link_down(9)fcoe_ctlr_send_keep_alive(9)fcoe_ctlr_encaps(9)fcoe_ctlr_els_send(9)fcoe_ctlr_age_fcfs(9)fcoe_ctlr_parse_adv(9)fcoe_ctlr_recv_adv(9)fcoe_ctlr_recv_els(9)fcoe_ctlr_recv_clr_vlink(9)fcoe_ctlr_recv(9)fcoe_ctlr_recv_handler(9)fcoe_ctlr_select(9)fcoe_ctlr_flogi_send_locked(9)fcoe_ctlr_flogi_retry(9)fcoe_ctlr_flogi_send(9)fcoe_ctlr_timeout(9)fcoe_ctlr_timer_work(9)fcoe_ctlr_recv_work(9)fcoe_ctlr_recv_flogi(9)fcoe_wwn_from_mac(9)fcoe_ctlr_rport(9)fcoe_ctlr_vn_send(9)fcoe_ctlr_vn_rport_callback(9)fcoe_ctlr_disc_stop_locked(9)fcoe_ctlr_disc_stop(9)fcoe_ctlr_disc_stop_final(9)fcoe_ctlr_vn_restart(9)fcoe_ctlr_vn_start(9)fcoe_ctlr_vn_parse(9)fcoe_ctlr_vn_send_claim(9)fcoe_ctlr_vn_probe_req(9)fcoe_ctlr_vn_probe_reply(9)fcoe_ctlr_vn_add(9)fcoe_ctlr_vn_lookup(9)fcoe_ctlr_vn_claim_notify(9)fcoe_ctlr_vn_claim_resp(9)fcoe_ctlr_vn_beacon(9)fcoe_ctlr_vn_age(9)fcoe_ctlr_vn_recv(9)fcoe_ctlr_vlan_parse(9)fcoe_ctlr_vlan_send(9)fcoe_ctlr_vlan_disc_reply(9)fcoe_ctlr_vlan_recv(9)fcoe_ctlr_disc_recv(9)fcoe_ctlr_vn_timeout(9)fcoe_ctlr_mode_set(9)fcoe_libfc_config(9)
literally the whole friend group π go read them, they're all iconic in their own way π
β and that's the page!! this one came straight out of ./drivers/scsi/fcoe, dated October 2026, and it's filed under fcoe_ctlr_vn_disc(9) β so if you ever need to find her again, that's the address, 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