ring_buffer_overrun_cpu(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ring_buffer_overrun_cpu(9) 💅

okay so bestie, welcome to the Kernel API Manual page for ring_buffer_overrun_cpu(9) — this is the one that gets the number of overruns caused by the ring buffer wrapping around, only if RB_FL_OVERWRITE is on. read that twice, okay? 💖

✨ NAME ✨

ring_buffer_overrun_cpu — get the number of overruns caused by the ring buffer wrapping around (only if RB_FL_OVERWRITE is on). 💫

heads up bestie: that RB_FL_OVERWRITE condition is not a vibe suggestion, it's literally part of the deal. 🫶

🌸 SYNOPSIS 🌸

no cap, the signature is literally this:

unsigned long ring_buffer_overrun_cpu (struct trace_buffer *buffer , int
cpu );

🎀 ARGUMENTS 🎀

  • buffer — the ring buffer. yes, that ring buffer. the main character. 👑
  • cpu — the per CPU buffer to get the number of overruns from. like, which CPU's overrun count are we grabbing? that one. 💅

🦋 SEE ALSO 🦋

the kernel file is ./kernel/trace/ring_buffer.c, and the whole linked entourage is right here — every single one, no skips, no cap:

mwah 💋 — this cutie came from the source path ./kernel/trace, dated October 2026, and the page is ring_buffer_overrun_cpu(9). byeee 🫶✨

📦 where this page comes from