linux-kernel - FW: FW: [PATCH 2.6.17.3] Memory Management: High-Memory Scalability Issue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <88299102B8C1F54BB5C8E47F30B2FBE2047C19A9@inblr-exch1.eu.uis.unisys.com>
Date:	Tue, 19 Sep 2006 15:13:53 +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-Memory Scalability Issue

-----Original Message-----
From: Andi Kleen [mailto:ak@...e.de] 
Sent: Tuesday, September 12, 2006 2:31 AM
To: Satapathy, Soumendu Sekhar
Cc: akpm@...l.org; torvalds@...l.org
Subject: Re: FW: [PATCH 2.6.17.3] Memory Management: High-Memory
Scalability Issue

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.

-Andi

-
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/