ice_devlink...d_layers_get(9)
π
ice_devlink_tx_sched_layers_get β like, the whole Kernel API Manual situation π
okay so bestie, you're looking at ice_devlink_tx_sched_layers_get(9) from the Kernel API Manual and honestly? it's giving "small function, big friend group" energy. it's a getter. it gets a thing. the thing is the tx_scheduling_layers parameter. that's the whole vibe. slay. β¨
β¨ NAME β¨
ice_devlink_tx_sched_layers_get β the one that gets the tx_scheduling_layers parameter π¦
lowkey iconic of it, ngl.
πΈ SYNOPSIS πΈ
int ice_devlink_tx_sched_layers_get (struct devlink *devlink , u32 id ,
struct devlink_param_gset_ctx *ctx , struct netlink_ext_ack *extack );
four arguments, one int coming back at you, no cap. copy it exactly like that if you're typing it out, bestie β character for character, i'm not playing π
π ARGUMENTS π
devlinkβ pointer to the devlink instance π« like, the actual object we're doing all this on. your main character, fr fr.idβ the parameter ID to set. yes, to set β that's literally what the manual says, don't come for me, i just report the facts π«Άctxβ the context where the parameter value gets stored. it's the little container the answer goes into, like a cute little gift box πextackβ netlink extended ACK structure. that's the thing that carries the extended acknowledgement info back through netlink. iykyk β
π₯ RETURN π₯
- zero on success π
- a negative value on failure π
that's it. that's the contract. zero = we ate. negative = we did not eat. periodt.
π SEE ALSO π
okay this is the part where the whole squad rolls up, because this function does not exist in a vacuum and the see-also list is genuinely enormous, so buckle up buttercup π§
and before we start β the kernel file lives at ./drivers/net/ethernet/intel/ice/devlink/devlink.c π
ice_devlink_info_get(9)ice_devlink_reload_empr_start(9)ice_devlink_reinit_down(9)ice_devlink_reload_down(9)ice_devlink_reload_empr_finish(9)ice_get_tx_topo_user_sel(9)ice_update_tx_topo_user_sel(9)ice_devlink_tx_sched_layers_set(9)ice_devlink_tx_sched_layers_validate(9)ice_tear_down_devlink_rate_tree(9)ice_enable_custom_tx(9)ice_traverse_tx_tree(9)ice_devlink_rate_init_tx_topology(9)ice_devlink_rate_clear_tx_topology(9)ice_set_object_tx_share(9)ice_set_object_tx_max(9)ice_set_object_tx_priority(9)ice_set_object_tx_weight(9)ice_get_pi_from_dev_rate(9)ice_devlink_reinit_up(9)ice_devlink_reload_up(9)ice_devlink_local_fwd_mode_to_str(9)ice_devlink_local_fwd_str_to_mode(9)ice_devlink_local_fwd_get(9)ice_devlink_local_fwd_set(9)ice_devlink_local_fwd_validate(9)ice_allocate_pf(9)ice_allocate_sf(9)ice_devlink_register(9)ice_devlink_unregister(9)ice_devlink_nvm_snapshot(9)ice_devlink_nvm_read(9)ice_devlink_devcaps_snapshot(9)ice_devlink_init_regions(9)ice_devlink_destroy_regions(9)
not me listing thirty-five functions in one go π but every single one of them is part of the squad and i would never leave a single one out. that's not the energy we're bringing in 2026.
and that's the page, bestie β¨π«Ά
this whole thing comes from the kernel source at ./drivers/net/ethernet/intel/i... and it's dated October 2026 β so yeah, fresh off the press, timestamped and everything. you're so welcome. go get that tx_scheduling_layers parameter. π
π
π¦ 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