Re: [PATCH 1/5] cpuset memory spread basic implementation

From: Christoph Lameter
Date: Mon Feb 06 2006 - 14:17:51 EST


On Mon, 6 Feb 2006, Andi Kleen wrote:
> On the other hand global interleaving actually worked for the page cache
> in production in SLES9, so it can't be that bad.

I would see it as an emergency measure given the bad control over locality
in SLES9 and the lack of an efficient zone reclaim.

> The question is just if it's a common situation. My guess is that just
> giving local memory priority but not throwing away all IO caches
> when the local node fills up would be a generally useful default policy.

We do not throw away "all IO caches". We take a portion of the inactive
list and scan for freeable pages.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/