From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andrew Morton <akpm@osdl.org>, Hugh Dickins <hugh@veritas.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.14-rc2-mm2] core remove PageReserved
Date: Tue, 11 Oct 2005 23:39:33 +1000 [thread overview]
Message-ID: <434BC095.4050305@yahoo.com.au> (raw)
In-Reply-To: <1129035883.23677.48.camel@localhost.localdomain>
Alan Cox wrote:
> On Maw, 2005-10-11 at 19:00 +1000, Nick Piggin wrote:
>
>>A last caveat: the ZERO_PAGE is now refcounted and managed with rmap
>>(and thus mapcounted and count towards shared rss).
>
>
> 32000 processes each with 2G mapped as zero pages appears to allow the
> refcount to overflow ?
>
That's right (though I count only 8192 required with 4K page size) -
close to impossible on 32-bit architectures, though not so the 64-bit
ones, which still use 32-bits for count and mapcount.
I was a bit worried about this too, but Hugh didn't think it was a
really big a deal - I guess because the real solution for the refcount
overflow on 64-bit is to expand the refcount type.
Note also that we can exclude ZERO_PAGE from being refcounted, which
may be desirable for a scalability perspective on big NUMA machines.
The aim with this patch is to provide a patch which is as simple as
possible in order to get the mechanism right. But you raise a valid
concern and we do need to discuss these peripheral issues and sort
them out before it gets merged upstream.
Thanks,
Nick
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2005-10-11 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 9:00 [PATCH 2.6.14-rc2-mm2] core remove PageReserved Nick Piggin
2005-10-11 13:04 ` Alan Cox
2005-10-11 13:39 ` Nick Piggin [this message]
2005-10-11 14:17 ` Hugh Dickins
2005-10-11 14:36 ` Nick Piggin
2005-10-11 14:38 ` Nick Piggin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=434BC095.4050305@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox