linux-kernel - Re: [PATCH -mm] change anon_vma linking to fix multi-process server 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: <4B747B6F.1090209@redhat.com>
Date:	Thu, 11 Feb 2010 16:49:35 -0500
From:	Rik van Riel <riel@...hat.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	"Luck, Tony" <tony.luck@...el.com>,
	Linux kernel Mailing List <linux-kernel@...r.kernel.org>,
	shak <dshaks@...hat.com>
Subject: Re: [PATCH -mm] change anon_vma linking to fix multi-process server
 scalability issue

On 02/11/2010 04:04 PM, Andrew Morton wrote:
> On Thu, 28 Jan 2010 00:20:00 -0500
> Rik van Riel<riel@...hat.com>  wrote:
>
>> The old anon_vma code can lead to scalability issues with heavily
>> forking workloads.  Specifically, each anon_vma will be shared
>> between the parent process and all its child processes.

Some test results:

Without the anon_vma changes, when AIM7 hits around 9.7k
users (on a test box with 16GB RAM and not quite enough IO),
the system ends up running >99% in system time, with every
CPU on the same anon_vma lock in the pageout code.

With these changes, AIM7 hits the cross-over point around
29.7k users.  This happens with ~99% IO wait time, there
never seems to be any spike in system time.  The anon_vma
lock contention appears to be resolved.

-- 
All rights reversed.
--
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/