Skip to content

RFC Reclaim during GFP_ATOMIC allocs

Christoph Lameter linux-mm lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest9 patches 36 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/9Allow reclaim via __GFP_NOMEMALLOC reclaimmm/vmscan.c+19 -30 replies
2/9Use NOMEMALLOC reclaim to allow reclaim if PF_MEMALLOC is setmm/page_alloc.c+11 -014 replies
3/9Make cond_rescheds conditional on __GFP_WAITmm/vmscan.c+12 -30 replies
4/9Atomic reclaim: Save irq flags in vmscan.cmm/vmscan.c+19 -1720 replies
5/9Save irqflags on taking the mapping lockmm/vmscan.c+6 -40 replies
6/9Disable irqs on taking the private_lockfs/buffer.c+32 -180 replies
7/9Save flags in swap.cmm/swap.c+13 -90 replies
8/9Reclaim on an atomic allocation if necessarymm/page_alloc.c+5 -10 replies
9/9Testing: Perform GFP_ATOMIC overallocationkernel/timer.c mm/vmscan.c+34 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [RFC 0/9] Reclaim during GFP_ATOMIC allocs

This is the extended version of the reclaim patchset. It enables reclaim from clean file backed pages during GFP_ATOMIC allocs. A bit invasive since may locks must now be taken with saving flags. But it works.

Tested by repeatedly allocating 12MB of memory from the timer interrupt.

Signature · 5 lines
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to [email protected].  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>