check_slab_...it_threshold(9)
π
check_slab_journal_commit_threshold β Kernel API Manual
okay so bestie, welcome to the Kernel API Manual β¨ this one's a little function from the dm-vdo corner of the kernel and honestly? it's giving vibe check on the journal π
πΈ NAME πΈ
check_slab_journal_commit_threshold β literally checks whether the journal is over the threshold, and if it is, forces the oldest slab journal tail block to commit π«Ά
no cap, that's the whole thing. it peeks at the journal, goes "hmm, are we past the line?", and if yes, it makes that oldest tail block commit. iconic behavior honestly π
β¨ SYNOPSIS β¨
void check_slab_journal_commit_threshold (struct recovery_journal *journal );
(yes, the spacing is exactly like that, we don't fix what the kernel gave us π)
π¦ ARGUMENTS π¦
journalβ The journal. that's it. that's the argument π it's astruct recovery_journal *and it's the journal we're checking. main character energy tbh π
π SEE ALSO π
bestie there are so many friends here, this function is clearly a social butterfly π§ literally the whole recovery-journal.c neighborhood showed up:
- Kernel file
./drivers/md/dm-vdo/recovery-journal.cβ plus a reference toLock Counters.(9) get_zone_count_ptr(9)get_counter(9)is_journal_zone_locked(9)vdo_release_recovery_journal_block_reference(9)pop_free_list(9)is_block_dirty(9)is_block_empty(9)is_block_full(9)assert_on_journal_thread(9)continue_waiter(9)has_block_waiters(9)suspend_lock_counter(9)check_for_drain_complete(9)notify_recovery_journal_of_read_only_mode(9)enter_journal_read_only_mode(9)vdo_get_recovery_journal_current_sequence_number(9)get_recovery_journal_head(9)compute_recovery_count_byte(9)finish_reaping(9)complete_reaping(9)handle_flush_error(9)initialize_journal_state(9)vdo_get_recovery_journal_length(9)reap_recovery_journal_callback(9)initialize_lock_counter(9)set_journal_tail(9)initialize_recovery_block(9)vdo_decode_recovery_journal(9)vdo_free_recovery_journal(9)vdo_initialize_recovery_journal_post_repair(9)vdo_get_journal_block_map_data_blocks_used(9)vdo_get_recovery_journal_thread_id(9)vdo_open_recovery_journal(9)vdo_record_recovery_journal(9)get_block_header(9)set_active_sector(9)advance_tail(9)initialize_lock_count(9)prepare_to_assign_entry(9)schedule_block_write(9)release_journal_block_reference(9)assign_entry(9)recycle_journal_block(9)continue_committed_waiter(9)notify_commit_waiters(9)recycle_journal_blocks(9)complete_write(9)add_queued_recovery_entries(9)write_block(9)write_blocks(9)vdo_add_recovery_journal_entry(9)is_lock_locked(9)reap_recovery_journal(9)vdo_acquire_recovery_journal_block_reference(9)vdo_release_journal_entry_lock(9)vdo_drain_recovery_journal(9)resume_lock_counter(9)vdo_resume_recovery_journal(9)vdo_get_recovery_journal_logical_blocks_used(9)vdo_get_recovery_journal_statistics(9)dump_recovery_block(9)vdo_dump_recovery_journal_statistics(9)
like, every single one of them. we love a well-connected function π«Άπ
and that's the page, bestie!! π this lil cutie lives in ./drivers/md/dm-vdo and the version stamp on it is October 2026 β so yeah, very much still check_slab_...it_threshold(9) era, slay β bye bestie, go read some journal code π
π¦ 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