From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, ak@suse.de,
Paul Mackerras <paulus@samba.org>
Subject: Re: [QUICKLIST 1/4] Quicklists for page table pages V5
Date: Wed, 11 Apr 2007 14:18:41 +1000 [thread overview]
Message-ID: <1176265121.8061.66.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0704102058420.18321@schroedinger.engr.sgi.com>
On Tue, 2007-04-10 at 21:04 -0700, Christoph Lameter wrote:
> On Tue, 10 Apr 2007, Benjamin Herrenschmidt wrote:
>
> > On Mon, 2007-04-09 at 11:25 -0700, Christoph Lameter wrote:
> >
> > > Quicklists for page table pages V5
> >
> > Looks interesting, but unfortunately not very useful at this point for
> > powerpc unless you remove the assumption that quicklists contain
> > pages...
>
> Then quicklists wont be as simple anymore.
>
> > On powerpc, we currently use kmem cache slabs (though that isn't
> > terribly node friendly) whose sizes depend on the page size.
> >
> > For a 4K page size kernel, we have 4 level page tables and use 2 caches,
> > PTE and PGD pages are 4K (thus are PAGE_SIZE'd), and PMD & PUD are 1K.
>
> PTE and PGD could be run via quicklists? With PTEs you cover the most
> common case. Quicklists using PGDs will allow to optimize using
> preconstructed pages.
>
> Its probably best to keep the slabs for the 1K pages.
>
> > For a 64K page size kernel, we have 3 level page tables and we use 3
> > caches: a PGD pages are 128 bytes (yeah, not big heh...), our pmd
> > pages are 32K (half a page) and PTE pages are PAGE_SIZE (64K).
>
> Ok so use quicklists for the PTEs and slab for the rest? A PGD of only 128
> bytes? Stuff one at the end of the mm_struct or the task struct? That way
> you can avoid allocation overhead.
Yeah, maybe... I need to think about it a bit more. I might be able to
make the PMD a full page too.
Ben.
--
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-04-11 4:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 18:25 Christoph Lameter
2007-04-09 18:25 ` [QUICKLIST 2/4] Quicklist support for IA64 Christoph Lameter
2007-04-09 18:25 ` [QUICKLIST 3/4] Quicklist support for x86_64 Christoph Lameter
2007-04-09 18:43 ` Andi Kleen
2007-04-09 18:46 ` Christoph Lameter
2007-04-09 18:49 ` Andi Kleen
2007-04-09 18:51 ` Christoph Lameter
2007-04-09 18:53 ` Andi Kleen
2007-04-09 18:56 ` Christoph Lameter
2007-04-09 21:28 ` Andrew Morton
2007-04-09 22:01 ` Christoph Lameter
2007-04-09 18:25 ` [QUICKLIST 4/4] Quicklist support for sparc64 Christoph Lameter, David Miller
2007-04-09 18:48 ` [QUICKLIST 1/4] Quicklists for page table pages V5 Andrew Morton
2007-04-09 18:50 ` Christoph Lameter
2007-04-09 21:27 ` Andrew Morton
2007-04-09 21:41 ` Andrew Morton
2007-04-09 22:03 ` Christoph Lameter
2007-04-10 0:26 ` William Lee Irwin III
2007-04-10 0:53 ` Christoph Lameter
2007-04-10 4:45 ` Benjamin Herrenschmidt
2007-04-11 4:04 ` Christoph Lameter
2007-04-11 4:18 ` Benjamin Herrenschmidt [this message]
2007-04-11 5:41 ` Paul Mackerras
2007-04-11 6:15 ` Benjamin Herrenschmidt
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=1176265121.8061.66.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paulus@samba.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