PAGE MOBILITY AND PLACEMENT HINTS(9)

🎀 PAGE MOBILITY AND PLACEMENT HINTS 🎀

okay so bestie, welcome to the Page mobility and placement hints(9) manual page from the Kernel API Manual — section 9, no cap. 💖 This one is all about the little flags that drop hints about how mobile a page is.

These flags provide hints about how mobile the page is. Pages with similar mobility are placed within the same pageblocks to minimise problems due to external fragmentation. ✨

• __GFP_MOVABLE (also a zone modifier) — indicates that the page can be moved by page migration during memory compaction, or can be reclaimed. 🔥
• __GFP_RECLAIMABLE — used for slab allocations that specify SLAB_RECLAIM_ACCOUNT, and whose pages can be freed via shrinkers. 🧚
• __GFP_WRITE — indicates the caller intends to dirty the page. Where possible, these pages will be spread between local zones to avoid all the dirty pages being in one zone (fair zone allocation policy). 💅
• __GFP_HARDWALL — enforces the cpuset memory allocation policy. 🫶
• __GFP_THISNODE — forces the allocation to be satisfied from the requested node with no fallbacks or placement policy enforcements. ⭐
• __GFP_ACCOUNT — causes the allocation to be accounted to kmemcg. 🌸

🌈 SEE ALSO 🌈

Kernel file ./tools/include/linux/gfp_types.h is the spot, and the vibes point you to:

• gfp_t(9)
• Watermark modifiers(9)
• Reclaim modifiers(9)
• Action modifiers(9)
• Useful GFP flag combinations(9)

okay that's the whole page, bestie. source/version: ./tools/include/linux; date: October 2026; page tag: Page mobili...cement hints(9). stay mobile, stay iconic 💅🦋✨