vdo_launch_flush(9)

🎀 NAME 🎀

vdo_launch_flush — Function called to start processing a flush request. And yes bestie, this is the vdo_launch_flush(9) page from the Kernel API Manual, and we are gonna get through it together 💖

---

✨ SYNOPSIS ✨

The signature is short, sweet, and iconic:

void vdo_launch_flush (struct vdo *vdo , struct bio *bio );

No cap, that's the whole flex 🦋

---

🌸 ARGUMENTS 🌸

• vdo — the vdo. That's the struct, bestie. Literally the vdo 💅
• bio — the bio containing an empty flush request. An empty flush request, living its best life inside a bio 🎀

---

🦋 DESCRIPTION 🦋

Okay so here's the vibe: vdo_launch_flush is called when we receive an empty flush bio from the block layer. It's also called before acknowledging a non-empty bio with the FUA flag set. That's the whole description, and it's lowkey important — it's the launch moment for processing a flush request 🔥

Empty flush bio from the block layer? Yep. Non-empty bio with the FUA flag set, before it gets acknowledged? Also yep. Periodt 💅

---

💅 SEE ALSO 💅

The lore continues in Kernel file ./drivers/md/dm-vdo/flush.c, and the whole squad is: assert_on_flusher_thread(9), as_flusher(9), completion_as_vdo_flush(9), vdo_waiter_as_flush(9), vdo_make_flusher(9), vdo_free_flusher(9), vdo_get_flusher_thread_id(9), finish_notification(9), flush_packer_callback(9), increment_generation(9), notify_flush(9), flush_vdo(9), check_for_drain_complete(9), vdo_complete_flushes(9), vdo_dump_flusher(9), initialize_flush(9), release_flush(9), vdo_complete_flush_callback(9), select_bio_queue(9), vdo_complete_flush(9), vdo_drain_flusher(9), vdo_resume_flusher(9). Every single one, bestie 👑

---

Source/version: ./drivers/md/dm-vdo · date: October 2026 — mwah, you ate this page 💋🫶