From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [QUICKLIST 1/5] Quicklists for page table pages V3
Date: Mon, 19 Mar 2007 17:55:24 -0700 [thread overview]
Message-ID: <20070319175524.812b2f5d.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0703191718220.13927@schroedinger.engr.sgi.com>
On Mon, 19 Mar 2007 17:44:28 -0700 (PDT)
Christoph Lameter <clameter@sgi.com> wrote:
> On Mon, 19 Mar 2007, Andrew Morton wrote:
>
> > Please provide proof that quicklists are superior to simply going direct to
> > the page allocator for these pages.
>
> See the patch. We are only touching 2 cachelines instead of 32. So even
> without considering the page allocator overhead and the slab allocator
> overhead (which will make the situation even better) its superior.
That's not proof, it is handwaving. I could wave right back at you and
claim that the benefit from returning a cache-hot pte page back to the page
allocator for reuse exceeds the benefit which you waved at me above.
You may well be right, but nothing is proven, afaict.
> > > I doubt it. The zeroing is a by product of our way of serializing pte
> > > handling. Its going to be difficult to change that.
> >
> > Nick didn't think so, and I don't see the problem either.
>
> You do not think that our current way of handling ptes is okay? If we do
> not zero the ptes then we need to separate munmap from process shutdown.
Yep. It's possible that process shutdown is a sufficiently common and
costly special-case for it to be worth special-casing.
> > We'll save on some bus traffic by avoiding the writeback, but how much
> > effect that will have we don't know. Presumably little.
>
> The advantage of the quicklists is that it does not require a rework of
> the pte serialization.
No, these are unrelated. We can get pte pages from the page allocator and
zero them without touching the munmap handling.
But it's possible that if we _were_ to optimise the munmap handling as
suggested, the end result would be superior.
next prev parent reply other threads:[~2007-03-20 0:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 23:37 Christoph Lameter
2007-03-19 23:37 ` [QUICKLIST 2/5] Quicklist support for IA64 Christoph Lameter
2007-03-19 23:37 ` [QUICKLIST 3/5] Quicklist support for i386 Christoph Lameter
2007-03-19 23:37 ` [QUICKLIST 4/5] Quicklist support for x86_64 Christoph Lameter
2007-03-19 23:37 ` [QUICKLIST 5/5] Quicklist support for sparc64 Christoph Lameter
2007-03-19 23:53 ` [QUICKLIST 1/5] Quicklists for page table pages V3 Andrew Morton
2007-03-19 23:57 ` Christoph Lameter
2007-03-20 0:07 ` Andrew Morton
2007-03-20 0:44 ` Christoph Lameter
2007-03-20 0:55 ` Andrew Morton [this message]
2007-03-20 1:03 ` Christoph Lameter
2007-03-20 1:32 ` Andrew Morton
2007-03-20 19:41 ` Christoph Lameter
2007-03-19 23:58 ` David Miller
2007-03-20 0:21 ` Andrew Morton
2007-03-20 1:06 ` Christoph Lameter
2007-03-20 3:12 ` Paul Mackerras
2007-03-20 19:43 ` Christoph Lameter
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=20070319175524.812b2f5d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@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
Powered by JetHome