ring_buffer_...rd_is_set_on(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ring_buffer_...rd_is_set_on(9)

okay so real talk, this one lives in the Kernel API Manual (yes that's the manual name, we're fancy now ✨) and it's honestly such a small little guy. Like, one function, one bool, one vibe check. Let's get into it 🫢


🌸 NAME 🌸

ring_buffer_record_is_set_on β€” returns true if the ring buffer is set writable, bestie. that's it. that's the whole job πŸ’–


✨ SYNOPSIS ✨

bool ring_buffer_record_is_set_on (struct trace_buffer *buffer );

πŸŽ€ ARGUMENTS πŸŽ€

  • buffer β€” the ring buffer you're checking, like "hey girl are you set to write-enabled or not" πŸ‘€

πŸ¦‹ DESCRIPTION πŸ¦‹

So the way this works: it returns true if the ring buffer is set writable by ring_buffer_record_on. 🫢

⚠️ But be so fr right now β€” this does NOT mean it's actually in a writable state. big difference, no cap. πŸ’€

Like, it can totally return true even when the ring buffer has been disabled by ring_buffer_record_disable, because that one is just a temporary disabling of the ring buffer. so the flag says "on" and the actual state is like... unbothered, moisturized, in its lane 🌈. don't get it twisted 😭


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./kernel/trace/ring_buffer.c

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), 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_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, she's short and she knows it πŸ’… mwah. shoutout to ./kernel/trace for hosting this icon and October 2026 for the timestamp β€” periodt. πŸ§šπŸ’œ

πŸ“¦ where this page comes from