ring_buffer_...d_events_cpu(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ring_buffer_dropped_events_cpu(9) — the Kernel API Manual, bestie edition 🎀

okay so real talk, this is a page straight out of the Kernel API Manual, and it's about finding out how many trace events your ring buffer straight-up ghosted you 👻 — like, dropped on the floor, never to be seen again. iconic behaviour tbh, but you gotta know the numbers. periodt.

✨ NAME ✨

ring_buffer_dropped_events_cpu — get the number of dropped events caused by the ring buffer filling up (only if RB_FL_OVERWRITE is off) 🌸

lowkey important caveat bestie: if RB_FL_OVERWRITE is on, this whole vibe changes — it's giving "overwriting oldest" energy, not "dropping" energy. iykyk 🫶

🌈 SYNOPSIS 🌈

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

like, that's the whole signature. she's compact, she's neat, she returns an unsigned long. we love a low-maintenance queen 👑

🦋 ARGUMENTS 🦋

  • buffer — The ring buffer 💖 like, the actual one. the main character of this whole operation. hand her over and we'll interrogate her.
  • cpu — The per CPU buffer to get the number of overruns from ✨ so like, each CPU has its own lil sub-buffer, and this is you picking which CPU's drama you wanna inspect. choose wisely, bestie 💅

👑 SEE ALSO 👑

okay this list is literally the whole extended friend group — like an infinity scarf of kernel tracing functions. every single one, no gatekeeping, fr fr 💜

also, if you wanna read the source yourself (and honestly, respect), it lives in the kernel file ./kernel/trace/ring_buffer.c 📖✨

and that's the whole page, bestie — go forth and count those dropped events 💖🌈👑

signing off from ./kernel/trace, dated October 2026 — this manual page ate and left no crumbs 🍓✨💅

📦 where this page comes from