resume_data_vio_pool(9)

💅 resume_data_vio_pool(9) 💅

okay bestie, welcome to the Kernel API Manual page for resume_data_vio_pool(9) — it’s giving kernel-core, and we’re reading it together 💖✨

🌸 NAME 🌸

resume_data_vio_pool — resume a data_vio pool. that’s the whole vibe, no cap 🫶

✨ SYNOPSIS ✨

the signature ate and left no crumbs:

void resume_data_vio_pool (struct data_vio_pool *pool , struct
       vdo_completion *completion );

🎀 ARGUMENTS 🎀

• pool — the data_vio pool. that’s the pool being resumed, periodt 💅
• completion — the completion to notify when the pool has resumed. it’s the “we’re back” ping 🔥

🦋 SEE ALSO 🦋

the whole linked squad, no skips, fr fr:

• Kernel file ./drivers/md/dm-vdo/data-vio.c
• Bio flags.(9)
• Introduction(9)
• check_for_drain_complete_locked(9)
• pack_status(9)
• set_data_vio_compression_status(9)
• cancel_data_vio_compression(9)
• attempt_logical_block_lock(9)
• launch_data_vio(9)
• schedule_releases(9)
• process_release_callback(9)
• initialize_data_vio(9)
• make_data_vio_pool(9)
• free_data_vio_pool(9)
• vdo_launch_bio(9)
• drain_data_vio_pool(9)
• dump_data_vio_pool(9)
• release_allocated_lock(9)
• release_logical_lock(9)
• finish_cleanup(9)
• get_data_vio_operation_name(9)
• data_vio_allocate_data_block(9)
• release_data_vio_allocation_lock(9)
• uncompress_data_vio(9)
• modify_for_partial_write(9)
• read_block(9)
• update_block_map(9)
• read_old_block_mapping(9)
• pack_compressed_data(9)
• compress_data_vio(9)
• launch_compress_data_vio(9)
• hash_data_vio(9)
• write_bio_finished(9)
• acknowledge_write_callback(9)
• allocate_block(9)
• handle_allocation_error(9)
• continue_data_vio_with_block_map_slot(9)

xoxo, source/version ./drivers/md/dm-vdo, date October 2026, page resume_data_vio_pool(9) 🎀✨