ring_buffer_nr_dirty_pages(9)

💅 ring_buffer_nr_dirty_pages(9) 💅

okay so bestie, welcome to the Kernel API Manual. This page is about ring_buffer_nr_dirty_pages, and it is literally the “how many pages are actually doing something” girlie. iconic behavior. ✨

🎀 NAME 🎀

ring_buffer_nr_dirty_pages — get the number of used pages in the ring buffer. periodt. 💅

✨ SYNOPSIS ✨

size_t ring_buffer_nr_dirty_pages (struct trace_buffer *buffer , int cpu
);

🫶 ARGUMENTS 🫶

• buffer — the <purple>ring_buffer</purple> you want the number of pages from. This is the main character of the call, ngl.
• cpu — the cpu of the ring_buffer you want the number of pages from. yes bestie, you gotta say which cpu’s ring buffer you’re asking about. 🦋

🦋 DESCRIPTION 🦋

It returns the number of pages that have content in the ring buffer. That’s it, that’s the whole flex. No cap, no extra lore: pages with content get counted. ✨

🌈 SEE ALSO 🌈

kernel file: ./kernel/trace/ring_buffer.c — the source, iykyk. 🫶

go read these next, bestie:

• 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_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)
• ring_buffer_resize(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)

that’s the whole page, bestie 🫶 source/version vibe: ./kernel/trace, date: October 2026, and the star of the show is ring_buffer_nr_dirty_pages(9). mwah 💋