t4_sge_eth_t...gress_update(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… t4_sge_eth_txq_egress_update πŸ’…

okay bestie, welcome to the Kernel API Manual ✨ this one's about an Ethernet TX queue doing its lil update dance, and honestly? it ate.


🌸 NAME 🌸

t4_sge_eth_txq_egress_update β€” handle Ethernet TX Queue update 🫢


✨ SYNOPSIS ✨

int t4_sge_eth_txq_egress_update (struct adapter *adap , struct
       sge_eth_txq *eq , int maxreclaim );

πŸŽ€ ARGUMENTS πŸŽ€

  • adap β€” the adapter πŸ’œ (the whole big device vibes)
  • eq β€” the Ethernet TX Queue ⭐ (the specific queue we're tending to)
  • maxreclaim β€” the maximum number of TX Descriptors to reclaim, or -1 πŸ”₯ (yes, literally -1, that's a whole thing)

πŸ¦‹ DESCRIPTION πŸ¦‹

So like, we're typically called here to update the state of an Ethernet TX Queue based on how far the hardware has gotten through consuming the TX Work Requests that we put on that Egress Queue. main character energy, honestly πŸ‘‘

This happens when we get Egress Queue Update messages β€” and also prophylactically in the regular timer-based Ethernet TX Queue maintenance. like, we're just checking in, no cap πŸ’…


🌈 SEE ALSO 🌈

kernel file ./drivers/net/ethernet/chelsio/cxgb4/sge.c β€” and bestie, the friend group is large, we love a big roster 🫢


ngl this page is short but she's booked and busy in sge.c πŸ’€

okay that's the whole thing, ily, go touch some TX descriptors πŸ§šπŸ’–

β€” from ./drivers/net/ethernet/chelsio..., dated October 2026, still serving looks in t4_sge_eth_t...gress_update(9) ⭐ slay, bye! πŸ“

πŸ“¦ where this page comes from