launch_compress_data_vio(9)

💖 launch_compress_data_vio(9) — Kernel API Manual 💖

🌸 NAME 🌸

launch_compress_data_vio — continue a write by attempting to compress the data. That’s the whole vibe, bestie. 💅

---

✨ SYNOPSIS ✨

okay so here’s the signature, exactly as it comes:

void launch_compress_data_vio (struct data_vio *data_vio );

---

🎀 ARGUMENTS 🎀

• data_vio — the data_vio. That’s it, that’s the argument. 🫶

---

🦋 DESCRIPTION 🦋

Okay so real talk: this is a re-entry point to vio_write, and it’s used by hash locks. That’s the tea. ✨

---

🔥 SEE ALSO 🔥

bestie, here’s the whole guest list — go read these too:

• 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)
• resume_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)
• 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)

---

Signed with all the sparkle from ./drivers/md/dm-vdo — Kernel API Manual — October 2026 💅🫶