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. -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [RFC 0/9] Reclaim during GFP_ATOMIC allocs
- From: Nick Piggin <[email protected]>
- [RFC 9/9] Testing: Perform GFP_ATOMIC overallocation
- From: Christoph Lameter <[email protected]>
- [RFC 7/9] Save flags in swap.c
- From: Christoph Lameter <[email protected]>
- [RFC 6/9] Disable irqs on taking the private_lock
- From: Christoph Lameter <[email protected]>
- [RFC 4/9] Atomic reclaim: Save irq flags in vmscan.c
- From: Christoph Lameter <[email protected]>
- [RFC 3/9] Make cond_rescheds conditional on __GFP_WAIT
- From: Christoph Lameter <[email protected]>
- [RFC 2/9] Use NOMEMALLOC reclaim to allow reclaim if PF_MEMALLOC is set
- From: Christoph Lameter <[email protected]>
- [RFC 5/9] Save irqflags on taking the mapping lock
- From: Christoph Lameter <[email protected]>
- [RFC 1/9] Allow reclaim via __GFP_NOMEMALLOC reclaim
- From: Christoph Lameter <[email protected]>
- [RFC 8/9] Reclaim on an atomic allocation if necessary
- From: Christoph Lameter <[email protected]>
- Re: [RFC 0/9] Reclaim during GFP_ATOMIC allocs
- Prev by Date: [RFC 5/9] Save irqflags on taking the mapping lock
- Next by Date: [RFC 2/9] Use NOMEMALLOC reclaim to allow reclaim if PF_MEMALLOC is set
- Previous by thread: Re: Documentation - How to debug ACPI Problems
- Next by thread: [RFC 8/9] Reclaim on an atomic allocation if necessary
- Index(es):
 |