public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC] 4-level page table directories.
Date: Fri, 28 Oct 2005 11:19:29 +0000	[thread overview]
Message-ID: <20051028111929.GA28317@lnx-holt.americas.sgi.com> (raw)
In-Reply-To: <20051027041709.GA13193@attica.americas.sgi.com>

On Fri, Oct 28, 2005 at 03:19:57PM +1000, Ian Wienand wrote:
> On Wed, Oct 26, 2005 at 11:17:09PM -0500, Robin Holt wrote:
> > I have started to work on 4-level page tables.  This boots.  I
> > make no further claims than that.
> 
> Do you need 4 level page tables for something?  I seem to remember it
> coming up before too, I'd certainly be interested in seeing any
> numbers you have.

We have an mpi library which makes memory available for multiple
processors.  We have squezzed as hard as we can to reduce the size of
that block.  Right now, the most processors we can service hits about
3192 (IIRC) which is more than enough for current hardware (limits to
2048 cpus).  In the next version of our hardware due out next spring,
that limit is raised to 16384 (IIRC).  To make the library work with
that size, we need to be able to mmap a larger region.

Unfortunately, we still want this to work with SUSE and RHEL
distributions.  Those distributors strongly favor a 16k page size.
To be able to use their standard kernel, we need to either convince the
entire community that 64k pages is right or we need to implement 4-level
page tables.

Thanks,
Robin

  parent reply	other threads:[~2005-10-28 11:19 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-27  4:17 [RFC] 4-level page table directories Robin Holt
2005-10-28  5:19 ` Ian Wienand
2005-10-28 11:19 ` Robin Holt [this message]
2005-10-28 23:23 ` Luck, Tony
2005-10-28 23:55 ` Chen, Kenneth W
2005-10-29  0:49 ` Grant Grundler
2005-10-29  2:18 ` David Mosberger-Tang
2005-11-01 12:13 ` Robin Holt
2005-11-01 15:41 ` David Mosberger-Tang
2005-11-02 10:35 ` Robin Holt
2005-11-02 13:26 ` Robin Holt
2005-11-02 16:11 ` Luck, Tony
2005-11-02 16:23 ` Robin Holt
2005-11-02 16:30 ` Luck, Tony
2005-11-02 17:16 ` Robin Holt
2005-11-02 18:59 ` David Mosberger-Tang
2005-11-02 22:26 ` Ian Wienand
2005-11-03  1:36 ` Gerald Pfeifer
2005-11-03  1:53 ` Chen, Kenneth W
2005-11-03  3:55 ` Jack Steiner
2005-11-03 16:36 ` Robin Holt
2005-11-03 19:59 ` Chen, Kenneth W
2005-11-04 17:58 ` Luck, Tony
2005-11-04 21:37 ` Robin Holt
2005-11-04 21:42 ` Chen, Kenneth W
2005-11-04 22:50 ` Chen, Kenneth W
2005-11-07 21:18 ` Luck, Tony
2005-11-08  0:22 ` Rohit Seth
2005-11-08 12:43 ` Robin Holt
2005-11-08 18:23 ` Boehm, Hans
2005-11-08 18:52 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-11-08 18:56 ` Rohit Seth
2005-11-08 19:36 ` Robin Holt
2005-11-08 20:07 ` Chen, Kenneth W
2005-11-08 20:27 ` Chen, Kenneth W
2005-11-08 22:09 ` Ian Wienand
2005-11-08 23:58 ` Gerald Pfeifer
2005-11-09  0:08 ` David Mosberger-Tang
2005-11-09  0:22 ` Rohit Seth
2005-11-09  0:46 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-11-09  1:18 ` Chen, Kenneth W
2005-11-09 12:11 ` Robin Holt
2005-11-09 14:29 ` Robin Holt
2005-11-09 18:22 ` Chen, Kenneth W
2005-11-09 18:39 ` Luck, Tony
2005-11-10  0:03 ` Gerald Pfeifer
2005-11-10  0:23 ` Jack Steiner
2005-11-10  0:27 ` Luck, Tony
2005-11-10  2:54 ` Jack Steiner
2005-11-10  9:13 ` Robin Holt

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=20051028111929.GA28317@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