fcoe_ctlr_solicit(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– fcoe_ctlr_solicit β€” bestie's guide to sending a FIP solicitation πŸ’–

ok so this one's a kernel API manual page, from the Kernel API Manual, and no cap it's a tiny little function but it's doing main character work behind the scenes in the FCoE world. let me break it down 🫢


✨ NAME ✨

fcoe_ctlr_solicit β€” literally just "Send a FIP solicitation" πŸŽ€ that's it, that's the whole vibe. it sends a solicitation, FIP-flavored.


🌸 SYNOPSIS 🌸

void fcoe_ctlr_solicit (struct fcoe_ctlr *fip , struct fcoe_fcf *fcf );

returns void, so like… it doesn't report back. it just does the thing πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • fip β€” the FCoE controller you're sending the solicitation on. it's the one actually doing the sending, the main character of this whole operation ✨
  • fcf β€” the destination FCF. and here's the cute lil twist: if it's NULL, a multicast solicitation gets sent instead. so like, no specific destination? cool, we broadcast to the group chat πŸ’Œ

πŸ”₯ SEE ALSO πŸ”₯

ok this section is LONG, like the whole friend group showed up. all of these live in the kernel file ./drivers/scsi/fcoe/fcoe_ctlr.c:

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_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_disc(9), fcoe_ctlr_vn_timeout(9), fcoe_ctlr_mode_set(9), fcoe_libfc_config(9)

yeah. literally all of them. iykyk πŸ’€


bestie note: the synopsis says the return type is void, so don't go looking for an exit status or a return value here β€” there isn't one to check πŸ™ˆ

and that's the page!! biggest slay goes to ./drivers/scsi/fcoe, which is where this whole thing lives, and the date on this gorgeous lil doc is October 2026 🌈 huge thanks to whoever wrote it, staying iconic since forever πŸ’œ

πŸ“¦ where this page comes from