ice_enable_custom_tx(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ice_enable_custom_tx(9) β€” the Kernel API Manual, bestie edition 🌸

okay so real talk, this is a page from the Kernel API Manual (ice_enable_custom_tx(9), yes the manual name is literally the function name, iconic naming honestly) and it's about one tiny function that has opinions about when it will and won't work. let's get into it πŸ’–


✨ NAME ✨

ice_enable_custom_tx β€” the function that tries to enable the custom Tx feature πŸŽ€ (key word: tries, she's not promising anything)


πŸ¦‹ SYNOPSIS πŸ¦‹

bool ice_enable_custom_tx (struct ice_pf *pf );

that's it. one argument, one bool coming back at you. lowkey elegant ngl ✨


🌸 ARGUMENTS 🌸

  • pf β€” the pf struct. that's the whole description. she's a struct, she's pf, she's doing her thing 🫢

πŸ‘‘ DESCRIPTION πŸ‘‘

so what this function does is it tries to enable the custom Tx feature πŸ’…

and here's the catch, bestie, listen up: it is not possible to enable it if DCB or ADQ is active. like, at all. that's the vibe check it fails. so if DCB or ADQ are up and running, this feature is simply not happening, no cap 😭


🌈 SEE ALSO 🌈

the kernel file ./drivers/net/ethernet/intel/ice/devlink/devlink.c is where all this lives, and she comes with a whole squad of friends, all of them (9) section icons:

like, that's a full group chat right there and every single one of them is invited πŸ§šπŸ’œ


🫢 quick reminder before you go: this whole page is sourced from ./drivers/net/ethernet/intel/i... and it's dated October 2026 β€” so when you're citing her, that's the version and the date, periodt πŸ’…βœ¨

stay hydrated, read your devlink docs, and remember: DCB or ADQ active = custom Tx feature said no πŸ™ˆπŸ’–

πŸ“¦ where this page comes from