drbd_bm_mark_for_writeout(9)

💅 drbd_bm_mark_for_writeout(9) — like, the Kernel API Manual edition ✨

okay bestie, buckle up, because this one is a tiny little function from the drbd_bm_mark_for_writeout(9) page of the Kernel API Manual and it is lowkey iconic 🎀

---

🌸 NAME 🌸

drbd_bm_mark_for_writeout — marks a page with a "hint" so it gets considered for writeout 💖

---

✨ SYNOPSIS ✨

void drbd_bm_mark_for_writeout (struct drbd_device *device , int page_nr );

that's the whole signature, no cap. returns void, so it's giving "I do the thing and I don't even need to tell you about it" energy 💅

---

🦋 ARGUMENTS 🦋

• device — the DRBD device. yes, that one. the main character 🫶
• page_nr — the bitmap page you're marking with the "hint" flag ⭐

---

🌈 DESCRIPTION 🌈

okay so here's the vibe: from inside an activity log transaction, we mark a few pages with these hints. then we call drbd_bm_write_hinted, which will only write out changed pages that are flagged with this mark 🔥

so like… the hint isn't doing the writing, it's just the little sticky note that says "hey, maybe look at me later" and then drbd_bm_write_hinted does the actual vibe check ✅ no wasted writes, we love efficiency, periodt 👑

---

💜 SEE ALSO 💜

• Kernel file ./drivers/block/drbd/drbd_bitmap.c 🗂️
• drbd_bm_write_lazy(9) 🧚

---

ok and one lil' note because I know you'd come for me: that SEE ALSO reference really is literally spelled drbd_bm_write_lazy(9) and the file really is literally ./drivers/block/drbd/drbd_bitmap.c — copy it exactly, don't get cute with it 🙈

---

and that's the page, bestie!! mwah 💋 this was written for the ./drivers/block/drbd section, dated October 2026, and it belongs to the drbd_bm_mark_for_writeout(9) page in the Kernel API Manual — go forth and mark those pages 🍓💖✨