node_dirty_ok(9)

💅 node_dirty_ok — a Kernel API Manual moment (section 9, bestie)

okay so picture this: it's a manpage, it's in the Kernel API Manual, and its whole entire personality is answering one (1) question. iconic behavior honestly. let's get into it 🎀

---

✨ NAME ✨

node_dirty_ok — literally just tells you whether a node is within its dirty limits. that's it. that's the job. she's a yes/no girlie and she's thriving 💖

---

🌸 SYNOPSIS 🌸

bool node_dirty_ok (struct pglist_data *pgdat );

look at her. one function, one argument, returns a bool. no cap, extremely clean. 🦋

---

💜 ARGUMENTS 💜

• pgdat — the node you wanna check. that's the whole assignment bestie, hand her the node and she'll tell you what's up ✨

---

🔥 RETURN 🔥

She gives you true when the dirty pages in pgdat are within the node's dirty limit 👑 and she gives you false if the limit is exceeded 💀. that's the vibe check. in bounds = true, over the line = false. periodt.

---

🌈 SEE ALSO 🌈

okay this is the group chat, these are her mutuals, all of them live in the kernel file ./mm/page-writeback.c 🫶 :

• node_dirtyable_memory(9)
• global_dirtyable_memory(9)
• domain_dirty_limits(9)
• global_dirty_limits(9)
• node_dirty_limit(9)
• __wb_calc_thresh(9)
• balance_dirty_pages_ratelimited_flags(9)
• balance_dirty_pages_ratelimited(9)
• wb_over_bg_thresh(9)
• tag_pages_for_writeback(9)
• writeback_iter(9)
• filemap_dirty_folio(9)
• folio_redirty_for_writepage(9)
• folio_mark_dirty(9)
• folio_wait_writeback(9)
• folio_wait_writeback_killable(9)
• folio_wait_stable(9)

like… the whole writeback friend group showed up. we love a supportive ecosystem 😭💅

---

ngl if you're poking around dirty page limits you're gonna wanna read basically all of those. iykyk 🧚

---

and that's the whole page bestie!! this little gem lives over in ./mm and the version we're looking at is dated October 2026 🌸 — same node_dirty_ok(9) energy, forever and always. mwah 💋✨