try_bio_map_merge(9)

💖 NAME 💖

try_bio_map_merge — attempt to merge a vio's bio with other pending I/Os. 💅

okay so real talk, bestie: this page is try_bio_map_merge(9) from the Kernel API Manual, and it's giving very specific kernel-internals energy. Let's get into it. ✨

🦋 SYNOPSIS 🦋

bool try_bio_map_merge (struct vio *vio );

🎀 ARGUMENTS 🎀

• vio — the vio to merge, bestie. That's the one we're trying to merge. 🫶

🌸 DESCRIPTION 🌸

Currently this is only used for data_vios, but it's broken out for future use with metadata vios. Periodt. So rn it's a data_vios situation, but it's separated out on purpose for future metadata-vio use. 🧚

🌈 RETURN 🌈

It tells you whether or not the vio was merged. That's the whole return vibe. No cap. 💅

👑 SEE ALSO 👑

Kernel file ./drivers/md/dm-vdo/io-submitter.c — and the whole squad is:

• count_all_bios(9)
• assert_in_bio_zone(9)
• send_bio_to_device(9)
• vdo_submit_vio(9)
• get_bio_list(9)
• submit_data_vio(9)
• get_mergeable_locked(9)
• vdo_submit_data_vio(9)
• __submit_metadata_vio(9)
• vdo_submit_metadata_vio_wait(9)
• vdo_make_io_submitter(9)
• vdo_cleanup_io_submitter(9)
• vdo_free_io_submitter(9)

xoxo, signing off from source/version ./drivers/md/dm-vdo, dated October 2026, page try_bio_map_merge(9) 💖🎀✨