[<prev] [next>] [day] [month] [year] [list]
Message-ID: <88299102B8C1F54BB5C8E47F30B2FBE2047C19AD@inblr-exch1.eu.uis.unisys.com>
Date: Tue, 19 Sep 2006 15:14:15 +0530
From: "Satapathy, Soumendu Sekhar" <Soumendu.Satapathy@...unisys.com>
To: <linux-kernel@...r.kernel.org>
Subject: FW: FW: [PATCH 2.6.17.3] Memory Management: High-MemoryScalability Issue
-----Original Message-----
From: Andrew Morton [mailto:akpm@...l.org]
Sent: Tuesday, September 12, 2006 4:07 AM
To: Andi Kleen
Cc: Satapathy, Soumendu Sekhar; torvalds@...l.org
Subject: Re: FW: [PATCH 2.6.17.3] Memory Management:
High-MemoryScalability Issue
On Mon, 11 Sep 2006 23:01:25 +0200
Andi Kleen <ak@...e.de> wrote:
> On Monday 11 September 2006 08:24, Satapathy, Soumendu Sekhar wrote:
> > Hi,
> >
> > http://lkml.org/lkml/2006/7/5/74
> >
> > This patch was tested successfully in a system with 4GB, 32GB and
64GB RAM.
> > Can it be considered for inclusion in the kernel.
>
> Thanks for your contribution to Linux.
>
> I'm not really deep enough into the high level swapping algorithm to
evaluate
> your patch competently, but your result looks promising. Normally this
> code is considered pretty fragile unfortunately so some more testing
> would be definitely needed. It's good that you gave a clear rationale
> on what you changed at least.
>
> I would recommend to do perhaps do some benchmarks on smaller machines
with
> the patch too (just to make sure there are no regressions on them)
and
> possible try
> a few more different workloads and then post on linux-mm@...ck.org.
There is
> where all the VM hackers tend to hang out.
>
Yes, I've tucked this patch away to take a closer look at, probably late
this week.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists