axienet_free_tx_chain(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– axienet_free_tx_chain(9) πŸ’–

okay so first things first, the vibe check: this is a page from the Kernel API Manual, and it's literally all about axienet_free_tx_chain, which β€” no cap β€” cleans up a whole series of linked TX descriptors. bestie, it's the janitor of the transmit ring and it does it gorgeously 🧹✨


✨ NAME ✨

axienet_free_tx_chain β€” Clean up a series of linked TX descriptors. πŸŽ€


🌸 SYNOPSIS 🌸

int axienet_free_tx_chain (struct axienet_local *lp , u32 first_bd , int
nr_bds , bool force , u32 *sizep , int budget );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • lp β€” Pointer to the axienet_local structure. yes, the main character struct πŸ’…
  • first_bd β€” Index of the first descriptor to clean up. start here, queen.
  • nr_bds β€” Max number of descriptors to clean up. it's giving "how many can we handle" energy.
  • force β€” Whether to clean descriptors even if not complete. lowkey aggressive but valid.
  • sizep β€” Pointer to a u32 accumulating the total byte count of completed packets (using skb->len). ⚠️ Ignored if NULL β€” so don't come crying if you pass nothing.
  • budget β€” NAPI budget (use 0 when not called from NAPI poll). fr fr, 0 is the move there.

πŸ”₯ DESCRIPTION πŸ”₯

Would either be called after a successful transmit operation, or after there was an error when setting up the chain. that's it, that's the whole plot β€” clean up after the good vibes or the mess, either way bestie's on it 🫢


⭐ RETURN ⭐

The number of packets handled. slay, a count πŸŽ‰


πŸ‘‘ SEE ALSO πŸ‘‘

if you wanna go down the rabbit hole, the source of truth is the kernel file ./drivers/net/ethernet/xilinx/xilinx_axienet_main.c β€” the whole friend group lives there:

iykyk πŸ’œ


and that's the whole page, bestie β€” mwah πŸ’‹ this lil number lives under ./drivers/net/ethernet/xilinx, dated October 2026, and it's a certified classic. go forth and free those descriptors πŸ§šβ€β™€οΈπŸ’–

πŸ“¦ where this page comes from