ice_lag_link_unlink(9)
β¨ ice_lag_link_unlink β¨
okay so this is a page straight out of the Kernel API Manual (section 9, the kernel-API girlies π
) and it's all about ice_lag_link_unlink(9) β a helper function that goes and calls lag_link/unlink for you so you don't have to. it's giving "middle management but make it slay" π
π NAME π
ice_lag_link_unlink β the helper function that calls lag_link/unlink, no cap π«Ά
πΈ SYNOPSIS πΈ
void ice_lag_link_unlink (struct ice_lag *lag , void *ptr );
that's it. that's the whole signature. two arguments, no return, iconic β¨
π¦ ARGUMENTS π¦
lagβ the lag info struct π like, this is the whole context bestie, it's where all the lag lore livesptrβ an opaque pointer, data of the mysterious kind π literally don't ask what's in it, it's opaque, that's the vibe, that's the point
ngl when the docs say "opaque" they mean it β you're not supposed to peek inside ptr, you just hand it over and trust the process π§
π₯ SEE ALSO π₯
okay so this is the part where the page lists, like, every single sibling this function has. and there are a LOT of them. family reunion energy. i'm putting them all here because i would never do you dirty and skip one π
The link / primary / backup girlies π
ice_lag_set_primary(9)ice_lag_set_bkup(9)netif_is_same_ice(9)ice_lag_config_eswitch(9)ice_netdev_to_lag(9)ice_lag_find_hw_by_lport(9)ice_pkg_has_lport_extract(9)ice_lag_find_primary(9)ice_lag_link(9)ice_lag_act_bkup_unlink(9)ice_lag_aa_unlink(9)
The filter committee π
ice_lag_cfg_fltr(9)ice_lag_cfg_dflt_fltr(9)ice_lag_cfg_drop_fltr(9)ice_lag_cfg_pf_fltrs_act_bkup(9)ice_lag_cfg_lp_fltr(9)ice_lag_cfg_pf_fltrs(9)ice_lag_preset_drop_fltr(9)ice_display_lag_info(9)
The queue & scheduling squad π
The VF-moving crew π¦ (they're always moving nodes around, it's their whole thing)
ice_lag_move_vf_node_tc(9)ice_lag_build_netdev_list(9)ice_lag_destroy_netdev_list(9)ice_lag_move_single_vf_nodes(9)ice_lag_move_vf_nodes(9)ice_lag_move_vf_nodes_cfg(9)ice_lag_prepare_vf_reset(9)ice_lag_complete_vf_reset(9)ice_lag_move_vf_nodes_tc_sync(9)ice_lag_move_vf_nodes_sync(9)ice_lag_reclaim_vf_tc(9)ice_lag_reclaim_vf_nodes(9)
The events & monitoring besties π
ice_lag_info_event(9)ice_lag_aa_failover(9)ice_lag_changeupper_event(9)ice_lag_monitor_link(9)ice_lag_monitor_act_bkup(9)ice_lag_aa_clear_spoof(9)ice_lag_monitor_act_act(9)ice_lag_monitor_info(9)ice_lag_chk_comp(9)ice_lag_monitor_rdma(9)ice_lag_process_event(9)ice_lag_event_handler(9)ice_lag_chk_disabled_bond(9)ice_lag_disable_sriov_bond(9)
The swid + prune list crowd β
The lifecycle / registration icons π
ice_lag_init_feature_support_flag(9)ice_lag_unregister(9)ice_register_lag_handler(9)ice_unregister_lag_handler(9)ice_create_lag_recipe(9)ice_init_lag(9)ice_deinit_lag(9)ice_lag_rebuild(9)ice_lag_is_switchdev_running(9)
and where does all this live? in the kernel file:
./drivers/net/ethernet/intel/ice/ice_lag.c
go read it, iykyk πβ¨
that's the whole page bestie, no filler, every last reference included π
kiss kiss, this was Kernel API Manual section 9, brought to you by ./drivers/net/ethernet/intel/ice, dated October 2026 β signed, ice_lag_link_unlink(9) herself π
β¨π
π¦ 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