From: Robin Holt <holt@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] Convert pgtable cache to slab
Date: Tue, 15 Feb 2005 12:02:13 +0000 [thread overview]
Message-ID: <20050215120213.GA20607@lnx-holt.americas.sgi.com> (raw)
In-Reply-To: <yq1wtxnprkq.fsf@wilson.mkp.net>
On Mon, Feb 14, 2005 at 11:18:21AM -0800, Luck, Tony wrote:
> >I have given this some more thought over the weekend and think I am
> >leaning more towards the quicklists. Its main attraction to me seems
> >to be the simplicity of design. The quicklists remain consistent with
> >what we are already familiar with. To make pte, pmd, and pgd entries
> >equivalent, I think I am going to propose a single quicklist for all
> >the different types of entries with a single add/remove function.
>
> What about the 4-level case? With 64K pages you end up with a surplus
> of bits if you use a full page for all pgd/pud/pmd/pte levels. Are
> you planning on just leaving unused space in the PGD so that everything
> is simple? It might be more efficient to slim down the number of bits
> in the pte level? Then the slab starts looking attractive again to
> handle the sub-page allocations.
For the 4-level case with 64k pages, what about just using 16k page
tables? That leaves us with 60 bits of addressable space which is fairly
close to the full space. It would make the tables consistently sized,
but I am not sure that is of much value. As you point out, the slab
would make that completely unnecessary.
Jack Steiner is trying to determine how much more expensive the off-node
page tables are than on node. Once we know that, we will know if a
per-cpu or per-node quicklist type arrangement is truely beneficial or
if a general use slab without node awareness will be adequate.
Thanks,
Robin
next prev parent reply other threads:[~2005-02-15 12:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 22:52 [PATCH] Convert pgtable cache to slab Martin K. Petersen
2004-10-19 4:08 ` Luck, Tony
2004-10-19 15:59 ` Martin K. Petersen
2005-02-10 20:29 ` Robin Holt
2005-02-10 20:38 ` Luck, Tony
2005-02-11 18:35 ` Robin Holt
2005-02-11 18:51 ` Luck, Tony
2005-02-11 19:33 ` Robin Holt
2005-02-14 16:33 ` Robin Holt
2005-02-14 19:18 ` Luck, Tony
2005-02-15 12:02 ` Robin Holt [this message]
2005-02-15 18:07 ` David Mosberger
2005-02-15 18:29 ` Luck, Tony
2005-02-15 19:31 ` Robin Holt
2005-02-15 19:46 ` David Mosberger
2005-02-15 19:57 ` Robin Holt
2005-02-15 19:59 ` Robin Holt
2005-02-15 20:03 ` David Mosberger
2005-02-15 20:08 ` Robin Holt
2005-02-15 20:15 ` William Lee Irwin III
2005-02-15 20:25 ` Luck, Tony
2005-02-15 20:26 ` David Mosberger
2005-02-17 17:22 ` Jack Steiner
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=20050215120213.GA20607@lnx-holt.americas.sgi.com \
--to=holt@sgi.com \
--cc=linux-ia64@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