node_dirty_limit(9)

💖 NAME 💖

okay so bestie, welcome to the node_dirty_limit(9) page from the Kernel API Manual 💅 this one is short and sweet: it's literally the maximum number of dirty pages allowed in a node. That's the whole vibe. No cap.

✨ SYNOPSIS ✨

unsigned long node_dirty_limit (struct pglist_data *pgdat );

🦋 ARGUMENTS 🦋

• pgdat — the node, periodt. That's the node you're asking about, bestie.

💅 RETURN 💅

It hands you back the maximum number of dirty pages allowed in a node, based on the node's dirtyable memory. Slay. ✨

🔥 SEE ALSO 🔥

The kernel file ./mm/page-writeback.c is holding all the related lore, and these besties are linked too:

• node_dirtyable_memory(9)
• global_dirtyable_memory(9)
• domain_dirty_limits(9)
• global_dirty_limits(9)
• node_dirty_ok(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)

xoxo, your kernel bestie 💖 source/version: ./mm · date: October 2026 · node_dirty_limit(9) 🎀