gsi_evt_ring_update(9)

🎀 gsi_evt_ring_update(9) 🎀

okay bestie, this is the page for gsi_evt_ring_update from the Kernel API Manual, and it's literally about updating transaction state from hardware. 💅 no cap.

---

✨ NAME ✨

gsi_evt_ring_update — Update transaction state from hardware

🦋 SYNOPSIS 🦋

void gsi_evt_ring_update (struct gsi *gsi , u32 evt_ring_id , u32 index
);

💅 ARGUMENTS 💅

• gsi — GSI pointer. It's the GSI pointer, bestie — that's the whole argument. 🫶
• evt_ring_id — Event ring ID. The event ring's ID, iykyk. ✨
• index — Event index in ring reported by hardware. Exactly that.

🌸 DESCRIPTION 🌸

okay so here's the tea. Events for RX channels contain the actual number of bytes received into the buffer. Every event has a transaction associated with it, and here we update transactions to record their actual received lengths. 🫶

When an event for a TX channel arrives, we use information in the transaction to report the number of requests and bytes that have been transferred. 🔥

This function is called whenever we learn that the GSI hardware has filled new events since the last time we checked. The ring's index field tells the first entry in need of processing. The index provided is the first unfilled event in the ring (following the last filled one). 👑

Events are sequential within the event ring, and transactions are sequential within the transaction array.

Note that index always refers to an element within the event ring. periodt. 💅

🔥 SEE ALSO 🔥

• Kernel file ./drivers/net/ipa/gsi.c
• The IPA Generic Software Interface(9)
• gsi_trans_tx_completed(9)
• gsi_isr(9)
• gsi_channel_poll_one(9)
• gsi_channel_poll(9)

---

okay bye bestie! source/version: ./drivers/net/ipa; date: October 2026 — mwah 💋✨