ice_create_lag_recipe(9)
π
ice_create_lag_recipe(9) β Kernel API Manual
okay bestie, welcome to the group chat β¨ this one's straight out of the Kernel API Manual, page for ice_create_lag_recipe(9). it's a little function from the Intel ice driver's LAG corner of the world, and we're gonna walk through it together, no cap π«Ά
πΈ NAME πΈ
ice_create_lag_recipe β
literally that's it, that's the whole NAME section π the docs don't give us a one-liner here, so we're not gonna invent one. respect the source, periodt.
β¨ SYNOPSIS β¨
int ice_create_lag_recipe (struct ice_hw *hw , u16 *rid , const u8
*base_recipe , u8 prio );
look at her π₯Ή four arguments, returns an int. she's giving "small function, big responsibility" energy.
π ARGUMENTS π
here's the vibe check on every single param, no skips:
hwβ pointer toHWstruct. the hardware handle, the main character of this whole saga πridβ pointer tou16to pass back recipe index. you hand her au16pointer, she hands you back a recipe index πbase_recipeβ recipe to base the new recipe on. the inspo, the blueprint, the mother recipe πprioβ priority for new recipe. where your new recipe sits in the pecking order π₯
π¦ DESCRIPTION π¦
so the doc line here is short and honestly a little unhinged but we're reporting it exactly as written:
function returns 0 on error
that's it. that's the whole description π ngl it's giving "the docs are tired". we're not gonna guess at anything beyond what's written β the page says 0 means error, and that's what we're telling you. fr fr, that's the whole description, so take it and go π
π SEE ALSO π
okay this list is iconic in the sense that it is extremely long and we love her for it. the source file lives at ./drivers/net/ethernet/intel/ice/ice_lag.c in the kernel tree β the whole LAG fam lives there, and here's every single sibling the page points you toward:
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_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_display_lag_info(9)ice_lag_qbuf_recfg(9)ice_lag_get_sched_parent(9)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_info_event(9)ice_lag_aa_qbuf_recfg(9)ice_lag_aa_move_vf_qs(9)ice_lag_aa_failover(9)ice_lag_reclaim_vf_tc(9)ice_lag_reclaim_vf_nodes(9)ice_lag_link(9)ice_lag_act_bkup_unlink(9)ice_lag_aa_unlink(9)ice_lag_link_unlink(9)ice_lag_set_swid(9)ice_lag_primary_swid(9)ice_lag_add_prune_list(9)ice_lag_del_prune_list(9)ice_lag_init_feature_support_flag(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_unregister(9)ice_lag_monitor_rdma(9)ice_lag_chk_disabled_bond(9)ice_lag_disable_sriov_bond(9)ice_lag_preset_drop_fltr(9)ice_lag_process_event(9)ice_lag_event_handler(9)ice_register_lag_handler(9)ice_unregister_lag_handler(9)ice_lag_move_vf_nodes_tc_sync(9)ice_lag_move_vf_nodes_sync(9)ice_init_lag(9)ice_deinit_lag(9)ice_lag_rebuild(9)ice_lag_is_switchdev_running(9)
like. that's the whole extended universe right there. iykyk π§π
π cute little sign-off π
and that's the page, bestie!! this one came from the kernel source tree at ./drivers/net/ethernet/intel/ice, and the version/date on the tin is October 2026 β so go forth, read your recipe functions, and remember: 0 means error up in here πβ¨ bye huns! ππ¦π
π¦ 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