enetc_unwind_tx_frame(9)

🎀 NAME 🎀

ok so bestie, meet enetc_unwind_tx_frame — the manual page that lives in the 9th section of the kernel API manual. her whole job? unwind the DMA mappings of a multi-buffer Tx frame. yes. that's the gig. she cleans up after your transmit frame so the DMA mappings don't just vibe there forever untethered 😭 iconic cleanup behavior honestly

✨ SYNOPSIS ✨

void enetc_unwind_tx_frame (struct enetc_bdr *tx_ring , int count , int i );

🫶 ARGUMENTS 🫶

• tx_ring — a pointer to the Tx ring where the buffer descriptors are actually hanging out. like, which ring are we doing this on, bestie? this one 💅
• count — how many Tx buffer descriptors need to get unmapped. the headcount of buffers that are about to be freed from their DMA mapping era 🦋
• i — the index of the last successfully mapped Tx buffer descriptor. lowkey the most important detail here — she's the last one that actually made it, so she's where the unwinding starts from 🔥

🌈 SEE ALSO 🌈

kernel file ./drivers/net/ethernet/freescale/enetc/enetc.c — go read the source, iykyk 🧚

and that's the whole page, periodt 💜 this little cutie came to you straight from the kernel file ./drivers/net/ethernet/freesca..., dated October 2026, in manual section 9 under the name enetc_unwind_tx_frame. mwah, drink some water, go unmap those buffers responsibly 🍓👑