ring_buffer_resize(9)
π« ring_buffer_resize(9) π«
okay bestie, so this is a page from the Kernel API Manual and it's about ring_buffer_resize β yes, exactly what it sounds like, we're changing the size of the ring buffer π lowkey a glow-up for your trace buffer, ngl.
β¨ NAME β¨
ring_buffer_resize β resize the ring buffer π
πΈ SYNOPSIS πΈ
int ring_buffer_resize (struct trace_buffer *buffer , unsigned long size
, int cpu_id );
ok so it's giving int, it takes three things, and you're gonna wanna read the next section fr fr π«Ά
π¦ ARGUMENTS π¦
bufferβ the buffer to resize. that's the main character right there πsizeβ the new size. the new lewk β¨cpu_idβ the cpu buffer to resize. yes, per-cpu, we love a specific queen π
π DESCRIPTION π
kay so the minimum size? it's 2 * rb_subbuf_capacity(buffer). that's the floor, bestie, don't go below it π
and the returns: 0 on success, and < 0 on failure. literal success vs. the flop era π
ngl, that's the whole description β short and iconic. periodt π
β SEE ALSO β
the kernel file is ./kernel/trace/ring_buffer.c β that's where the magic lives π§ and here's the whole friend group, no one left out, fr fr:
ring_buffer_event_length(9),ring_buffer_event_data(9),rb_page_capacity(9),rb_subbuf_capacity(9),rb_subbuf_max_data_size(9),rb_subbuf_start(9),ring_buffer_event_time_stamp(9),ring_buffer_nr_dirty_pages(9),ring_buffer_wake_waiters(9),ring_buffer_wait(9),ring_buffer_poll_wait(9),rb_check_pages(9),rb_validate_buffer(9),__ring_buffer_alloc(9),__ring_buffer_alloc_range(9),__ring_buffer_alloc_remote(9),ring_buffer_free(9),rb_update_event(9),ring_buffer_nest_start(9),ring_buffer_nest_end(9),ring_buffer_unlock_commit(9),ring_buffer_lock_reserve(9),ring_buffer_discard_commit(9),ring_buffer_write(9),ring_buffer_record_disable(9),ring_buffer_record_enable(9),ring_buffer_record_off(9),ring_buffer_record_on(9),ring_buffer_record_is_on(9),ring_buffer_record_is_set_on(9),ring_buffer_record_is_on_cpu(9),ring_buffer_record_disable_cpu(9),ring_buffer_record_enable_cpu(9),ring_buffer_oldest_event_ts(9),ring_buffer_bytes_cpu(9),ring_buffer_entries_cpu(9),ring_buffer_overrun_cpu(9),ring_buffer_commit_overrun_cpu(9),ring_buffer_dropped_events_cpu(9),ring_buffer_read_events_cpu(9),ring_buffer_entries(9),ring_buffer_overruns(9),ring_buffer_iter_reset(9),ring_buffer_iter_empty(9),ring_buffer_peek(9),ring_buffer_iter_peek(9),ring_buffer_consume(9),ring_buffer_read_start(9),ring_buffer_read_finish(9),ring_buffer_iter_advance(9),ring_buffer_size(9),ring_buffer_max_event_size(9),ring_buffer_reset_cpu(9),ring_buffer_reset_online_cpus(9),ring_buffer_reset(9),ring_buffer_empty(9),ring_buffer_empty_cpu(9),ring_buffer_swap_cpu(9),ring_buffer_alloc_read_page(9),ring_buffer_free_read_page(9),ring_buffer_read_page(9),ring_buffer_read_page_data(9),ring_buffer_read_page_size(9),ring_buffer_subbuf_size_get(9),ring_buffer_subbuf_order_get(9),ring_buffer_subbuf_order_set(9)
and that's the whole vibe check π this page lives in ./kernel/trace, dated October 2026, and it's still ring_buffer_resize(9) at the end of the day β slay, go resize something responsibly, bestie πΈπ
π«Ά
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms