ice_tso(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ice_tso(9) β€” your girl's guide to the kernel API manual

okay bestie, welcome to ice_tso β€” yes that's the page, and yes it lives in the kernel API manual (section 9, we love a syscall-adjacent-adjacent vibe 🧚). buckle up, this one's short but she's important.


✨ SYNOPSIS ✨

int ice_tso (struct ice_tx_buf *first , struct ice_tx_offload_params *off );

that's it. that's the whole signature. no notes. πŸŽ€


🌸 ARGUMENTS 🌸

  • first β€” pointer to struct ice_tx_buf. she's literally the first one, the main character, the beginning of the buffer chain 🫢
  • off β€” pointer to struct that holds offload parameters. all the offload-y details live in here, iykyk πŸ’œ

πŸ”₯ DESCRIPTION πŸ”₯

so here's the tea: this function returns 0 or error (negative) if TSO can't happen, and 1 otherwise.

that's the whole description, no cap. not me being obsessed with how tidy that is 😭

lowkey important vibe check: negative return values mean TSO is a no-go, and a 1 means it's happening. don't mix those up or it's giving bug report πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

the kernel file, fr fr β€” ./drivers/net/ethernet/intel/ice/ice_txrx.c

and now, presenting, the entire friend group πŸ’… (every single one of them):

like, the whole roster. no one left out. periodt πŸ¦‹


okay that's the page!! mwah πŸ’– this iconic little entry came to you from ./drivers/net/ethernet/intel/ice, dated October 2026 β€” stay hydrated, read your manpages, and remember: return 1 means slay, negative means not today bestie 🌈⭐

πŸ“¦ where this page comes from