ice_vf_lan_overflow_event(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ice_vf_lan_overflow_event (9) β€” Kernel API Manual 🫢

okay so bestie, welcome to the ice era of the kernel API manual, because we're about to read the page for ice_vf_lan_overflow_event and honestly? it's giving "small function, very specific job" and i respect it so much ✨


🌸 NAME 🌸

ice_vf_lan_overflow_event β€” handle a LAN overflow event for a VF, that's literally the whole gig πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

void ice_vf_lan_overflow_event (struct ice_pf *pf , struct
       ice_rq_event_info *event );

πŸ’– ARGUMENTS πŸ’–

  • pf β€” the PF that the LAN overflow event happened on, i.e. the parent-function main character in this whole situation πŸ‘‘
  • event β€” the structure holding the event information for the LAN overflow event. it's the receipt, basically 🧾

✨ DESCRIPTION ✨

so here's the vibe check πŸ” β€” this function figures out whether the LAN overflow event was actually caused by a VF queue.

  • if it was not caused by a VF? do nothing. not a single thing. we move on with our lives πŸ™ˆ
  • if a VF caused this LAN overflow event? trigger a reset on the offending VF πŸ’€ periodt, that VF is getting sent to the timeout corner.

no cap, that's the entire plot. short page, clear stakes 🎯


🌈 SEE ALSO 🌈

kernel file ./drivers/net/ethernet/intel/ice/ice_sriov.c β€” that's where the source lives, iykyk πŸ“

and now the friend group, all of them, no one left out 🫢:

ice_free_vf_entries(9), ice_free_vf_res(9), ice_dis_vf_mappings(9), ice_free_vfs(9), ice_vf_vsi_setup(9), ice_ena_vf_msix_mappings(9), ice_ena_vf_q_mappings(9), ice_ena_vf_mappings(9), ice_calc_vf_reg_idx(9), ice_set_per_vf_res(9), ice_init_vf_vsi_res(9), ice_start_vfs(9), ice_sriov_free_vf(9), ice_sriov_clear_reset_state(9), ice_sriov_clear_mbx_register(9), ice_sriov_trigger_reset_register(9), ice_sriov_poll_reset_status(9), ice_sriov_clear_reset_trigger(9), ice_sriov_post_vsi_rebuild(9), ice_create_vf_entries(9), ice_ena_vfs(9), ice_pci_sriov_ena(9), ice_check_sriov_allowed(9), ice_sriov_get_vf_total_msix(9), ice_sriov_set_msix_vec_count(9), ice_sriov_configure(9), ice_process_vflr_event(9), ice_get_vf_from_pfq(9), ice_globalq_to_pfq(9), ice_set_vf_spoofchk(9), ice_get_vf_cfg(9), __ice_set_vf_mac(9), ice_set_vf_mac(9), ice_setup_vf_trust(9), ice_set_vf_trust(9), ice_set_vf_link_state(9), ice_calc_all_vfs_min_tx_rate(9), ice_min_tx_rate_oversubscribed(9), ice_set_vf_bw(9), ice_get_vf_stats(9), ice_is_supported_port_vlan_proto(9), ice_set_vf_port_vlan(9), ice_print_vf_rx_mdd_event(9), ice_print_vf_tx_mdd_event(9), ice_print_vfs_mdd_events(9), ice_restore_all_vfs_msi_state(9)


and that's the page!! πŸŽ€ source path ./drivers/net/ethernet/intel/ice, dated October 2026, and the whole thing is filed under ice_vf_lan_overflow_event(9) β€” slay, go read the other 45 pages now, i'll wait πŸ’œβ­

πŸ“¦ where this page comes from