initialize_vio(9)

💖 initialize_vio(9) 💖

okay so bestie, this is the initialize_vio(9) page from the Kernel API Manual — and yes, it’s giving “tiny but crucial setup function” energy. No cap. 🫶

🌸 NAME 🌸

initialize_vio — Initialize a vio. literally that’s the whole name, and it ate. 💅

✨ SYNOPSIS ✨

bestie, here’s the exact signature, copy it character-for-character or the vibe check will fail:

void initialize_vio (struct vio *vio , struct bio *bio , unsigned int
block_count , enum vio_type vio_type , enum vio_priority priority ,
struct vdo *vdo );

🎀 ARGUMENTS 🎀

okay so every single one of these matters, bestie, don’t skip:

• vio — the vio you’re initializing. That’s the main character right here. ✨
• bio — the bio this vio should use for its I/O. It’s literally the I/O ride-or-die. 🚗
• block_count — the size of this vio in vdo blocks. Count those blocks, periodt. 🧚
• vio_type — the vio type. Yep, the type. No cap. 💅
• priority — the relative priority of the vio. So it knows its ranking, lowkey important. 👑
• vdo — the vdo for this vio. The whole vdo, bestie. 🫶

🦋 SEE ALSO 🦋

also peep the Kernel file ./drivers/md/dm-vdo/vio.h, plus these iconique references — all of them, fr fr:

• as_vio(9)
• get_vio_bio_zone_thread_id(9)
• assert_vio_in_bio_zone(9)
• is_data_vio(9)
• get_metadata_priority(9)
• continue_vio(9)
• continue_vio_after_io(9)

this cutie came from ./drivers/md/dm-vdo, October 2026 — initialize_vio(9), signing off 💅✨