ring_buffer_write(9)

📦 version 7.3.1, in nixpkgs unstable

💖 NAME 💖

ring_buffer_write — write data to the buffer without reserving. That’s the whole vibe: no reserve step, just write, bestie.

Okay so welcome to the Kernel API Manual page for ring_buffer_write(9). This is your shortcut when you already have the data and just want it in the ring buffer. Let’s get into it 💅✨

✨ SYNOPSIS ✨

int ring_buffer_write (struct trace_buffer *buffer , unsigned long
       length , void *data );

🎀 ARGUMENTS 🎀

  • buffer — the ring buffer you’re writing into.
  • length — the length of the data being written (excluding the event header).
  • data — the actual data to write to the buffer.

🦋 DESCRIPTION 🦋

Okay so picture this: this is basically ring_buffer_lock_reserve and ring_buffer_unlock_commit doing a fusion dance into one function. If you already have the data ready to write to the buffer, it may be easier to simply call this function. Lowkey convenient, fr fr.

Note, like ring_buffer_lock_reserve, the length is the length of the data and not the length of the event which would hold the header. Read that again, bestie: data length, not event-with-header length. Periodt. 💅

💜 SEE ALSO 💜

Kernel file ./kernel/trace/ring_buffer.c — and the whole squad:

mwah 💋 — source/version: ./kernel/trace; date: October 2026; page: ring_buffer_write(9). Stay iconic, bestie 💅✨

📦 where this page comes from