From: Christoph Lameter <clameter@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [QUICKLIST 1/5] Quicklists for page table pages V4
Date: Mon, 26 Mar 2007 09:52:17 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0703260938520.3297@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070323222133.f17090cf.akpm@linux-foundation.org>
On Fri, 23 Mar 2007, Andrew Morton wrote:
> On Fri, 23 Mar 2007 10:54:12 -0700 (PDT) Christoph Lameter <clameter@sgi.com> wrote:
>
> > Here are the results of aim9 tests on x86_64. There are some minor performance
> > improvements and some fluctuations.
>
> There are a lot of numbers there - what do they tell us?
That there are performance improvements because of quicklists.
> So what has changed here? From a quick look it appears that x86_64 is
> using get_zeroed_page() for ptes, puds and pmds and is using a custom
> quicklist for pgds.
x86_64 is only using a list in order to track pgds. There is no
quicklist without this patchset.
> After your patches, x86_64 is using a common quicklist allocator for puds,
> pmds and pgds and continues to use get_zeroed_page() for ptes.
x86_64 should be using quicklists for all ptes after this patch. I did not
convert pte_free() since it is only used for freeing ptes during races
(see __pte_alloc). Since pte_free gets passed a page struct it would require
virt_to_page before being put onto the freelist. Not worth doing.
Hmmm... Then how does x86_64 free the ptes? Seems that we do
free_page_and_swap_cache() in tlb_remove_pages. Yup so ptes are not
handled which limits the speed improvements that we see.
> My question is pretty simple: how do we justify the retention of this
> custom allocator?
I would expect this functionality (never thought about it as an allocator)
to extract common code from many arches that use one or the other form of
preserving zeroed pages for page table pages. I saw lots of arches doing
the same with some getting into trouble with the page structs. Having a
common code base that does not have this issue would clean up the kernel
and deal with the slab issue.
> Because simply removing it is the preferable way of fixing the SLUB
> problem.
That would reduce performance. I did not think that a common feature
that is used throughout many arches would need rejustification.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-03-26 16:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 6:28 Christoph Lameter
2007-03-23 6:28 ` [QUICKLIST 2/5] Quicklist support for IA64 Christoph Lameter
2007-03-23 6:28 ` [QUICKLIST 3/5] Quicklist support for i386 Christoph Lameter
2007-03-23 6:28 ` [QUICKLIST 4/5] Quicklist support for x86_64 Christoph Lameter
2007-03-23 6:29 ` [QUICKLIST 5/5] Quicklist support for sparc64 Christoph Lameter, David Miller
2007-03-23 6:39 ` [QUICKLIST 1/5] Quicklists for page table pages V4 Andrew Morton
2007-03-23 6:52 ` Christoph Lameter
2007-03-23 7:48 ` Andrew Morton
2007-03-23 11:23 ` William Lee Irwin III
2007-03-23 14:58 ` Christoph Lameter
2007-03-23 11:29 ` William Lee Irwin III
2007-03-23 14:57 ` William Lee Irwin III
2007-03-23 19:17 ` William Lee Irwin III
2007-03-23 11:39 ` Nick Piggin
2007-03-24 5:14 ` Andrew Morton
2007-03-23 15:08 ` Christoph Lameter
2007-03-23 17:54 ` Christoph Lameter
2007-03-24 6:21 ` Andrew Morton
2007-03-26 16:52 ` Christoph Lameter [this message]
2007-03-26 18:14 ` Christoph Lameter
2007-03-26 18:26 ` Andrew Morton
2007-03-27 1:06 ` William Lee Irwin III
2007-03-27 1:22 ` Christoph Lameter
2007-03-27 1:45 ` David Miller, William Lee Irwin III
2007-03-27 11:19 ` William Lee Irwin III
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=Pine.LNX.4.64.0703260938520.3297@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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