Marcelo Tosatti <[email protected]> wrote: > > The fair approach would be to have the > number of pages to reclaim also relative to zone size. > > sc->nr_to_reclaim = (zone->present_pages * sc->swap_cluster_max) / > total_memory; You can try it, but that shouldn't matter. SWAP_CLUSTER_MAX is just a batching factor used to reduce CPU consumption. If you make it twice as bug, we run DMA-zone reclaim half as often - it should balance out. - 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: [PATCH 0/4] Swap migration V3: Overview
- From: Marcelo Tosatti <[email protected]>
- Re: [PATCH 0/4] Swap migration V3: Overview
- References:
- [PATCH 0/4] Swap migration V3: Overview
- From: Christoph Lameter <[email protected]>
- Re: [PATCH 0/4] Swap migration V3: Overview
- From: Magnus Damm <[email protected]>
- Re: [PATCH 0/4] Swap migration V3: Overview
- From: Marcelo Tosatti <[email protected]>
- Re: [PATCH 0/4] Swap migration V3: Overview
- From: Magnus Damm <[email protected]>
- Re: [PATCH 0/4] Swap migration V3: Overview
- From: Marcelo Tosatti <[email protected]>
- Re: [PATCH 0/4] Swap migration V3: Overview
- From: Magnus Damm <[email protected]>
- Re: [PATCH 0/4] Swap migration V3: Overview
- From: Marcelo Tosatti <[email protected]>
- Re: [PATCH 0/4] Swap migration V3: Overview
- From: Magnus Damm <[email protected]>
- Re: [PATCH 0/4] Swap migration V3: Overview
- From: Marcelo Tosatti <[email protected]>
- [PATCH 0/4] Swap migration V3: Overview
- Prev by Date: Re: Notifier chains are unsafe
- Next by Date: Re: 4GB memory and Intel Dual-Core system
- Previous by thread: Re: [PATCH 0/4] Swap migration V3: Overview
- Next by thread: Re: [PATCH 0/4] Swap migration V3: Overview
- Index(es):