get_thread_id_for_phase(9)

🎀 get_thread_id_for_phase(9) 🎀

okay so this is the get_thread_id_for_phase(9) page from the Kernel API Manual, and it’s giving “tiny function, very specific job” energy 💖✨

🌸 NAME 🌸

get_thread_id_for_phase — grabs the thread id for whichever phase the admin operation currently in progress is on 💅

✨ SYNOPSIS ✨

thread_id_t get_thread_id_for_phase (struct vdo *vdo );

🫶 ARGUMENTS 🫶

• vdo — the vdo. That’s the argument, bestie. No cap, that’s the whole list 🫶

👀 SEE ALSO 👀

also go peek at these icons, iykyk:

• the Kernel file ./drivers/md/dm-vdo/dm-vdo-target.c
• free_device_config(9)
• get_version_number(9)
• parse_bool(9)
• parse_memory(9)
• parse_slab_size(9)
• process_one_thread_config_spec(9)
• parse_one_thread_config_spec(9)
• parse_thread_config_string(9)
• process_one_key_value_pair(9)
• parse_one_key_value_pair(9)
• parse_key_value_pairs(9)
• parse_optional_arguments(9)
• handle_parse_error(9)
• parse_device_config(9)
• advance_phase(9)
• finish_operation_callback(9)
• decode_from_super_block(9)
• decode_vdo(9)
• pre_load_callback(9)
• get_bit_array_size(9)
• grow_bit_array(9)
• allocate_instance(9)
• check_may_grow_physical(9)
• grow_layout(9)
• validate_new_device_config(9)
• write_super_block_for_suspend(9)
• suspend_callback(9)
• was_new(9)
• requires_repair(9)
• get_load_type(9)
• load_callback(9)
• handle_load_error(9)
• write_super_block_for_resume(9)
• resume_callback(9)
• grow_logical_callback(9)
• handle_logical_growth_error(9)
• perform_grow_logical(9)
• copy_partition(9)
• grow_physical_callback(9)
• handle_physical_growth_error(9)
• perform_grow_physical(9)
• apply_new_vdo_configuration(9)

mwah 💋 this lil page came from source/version ./drivers/md/dm-vdo and is dated October 2026, and the page itself is get_thread_id_for_phase(9) — periodt 🌈💜