ring_buffer_...uf_order_set(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ring_buffer_subbuf_order_set(9)

okay so this little icon is from the Kernel API Manual, and bestie, it's literally about resizing ring buffer pages. tiny function, big vibes. let's get into it 🫶

✨ NAME ✨

ring_buffer_subbuf_order_set — set the size of ring buffer sub page. no cap, that's the whole job 💖

🌸 SYNOPSIS 🌸

int ring_buffer_subbuf_order_set (struct trace_buffer *buffer , int order );

🎀 ARGUMENTS 🎀

  • buffer — the ring_buffer you're giving a whole new page size to. main character energy, honestly 👑
  • order — the order of the system pages that fit inside one sub buffer page. this is the number that does the actual slaying 🔥

🦋 DESCRIPTION 🦋

okay so by default, one ring buffer page = one system page. that's the standard. that's the baseline. that's the pre-glow-up era 💀

this API lets you set a new size for the ring buffer page, and the size has to be an order of the system page size — that's literally why the input parameter is called order: it's the order of system pages that get allocated for one ring buffer page. like so:

  • 0 — 1 system page
  • 1 — 2 system pages
  • 3 — 4 system pages

...and so on, iykyk 🌈

it Returns 0 on success, or < 0 in case of an error. so like, zero means slay, negative means we're not okay 😭

⭐ SEE ALSO ⭐

the whole friend group, fr fr — and also the kernel file ./kernel/trace/ring_buffer.c:

bestie this page is from ./kernel/trace, dated October 2026 — that's the source/version and the date, and yes i'm mentioning them because the footer said so 💜

that's the whole page!! go forth and resize ur sub pages responsibly, ily 🧚✨🎀

📦 where this page comes from