public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin LaHaise <bcrl@redhat.com>
To: Gerrit Huizenga <gerrit@us.ibm.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"M. Edward Borasky" <znmeb@aracnet.com>,
	Harald Holzer <harald.holzer@eunet.at>,
	linux-kernel@vger.kernel.org
Subject: Re: i686 SMP systems with more then 12 GB ram with 2.4.x kernel ?
Date: Sun, 6 Jan 2002 03:20:30 -0500	[thread overview]
Message-ID: <20020106032030.A27926@redhat.com> (raw)
In-Reply-To: <E16LTvs-00016I-00@the-village.bc.nu> <E16Lslt-0001aG-00@w-gerrit2>
In-Reply-To: <E16Lslt-0001aG-00@w-gerrit2>; from gerrit@us.ibm.com on Wed, Jan 02, 2002 at 01:17:59PM -0800

On Wed, Jan 02, 2002 at 01:17:59PM -0800, Gerrit Huizenga wrote:
> I don't know if there are real examples of large memory systems
> exhausting the ~1 GB of kernel virtual address space on machines
> with > 12-32 GB of physical memory (we had this problem in PTX which
> created the need for a larger kernel virtual address space in some
> contexts).

The ~800MB or so of kernel address space is exhausted with struct page 
entries around 48GB of physical memory or so

SGI's original highmem patch switched page tables on entry to kernel 
space, so there is code already tested that we can borrow.  But I'm 
not sure if it's worth it as the overhead it adds makes life really 
suck: we would lose the ability to use global pages, as well as always 
encounter tlb misses on the kernel<->userspace transition.  PAE shows 
up as a 5% performance loss on normal loads, and this would make it 
worse.  We're probably better off implementing PSE.  Of course, making 
these kinds of choices is hard without actual statistics of the 
usage patterns we're targetting.

> Would be nice to have a config option like "CONFIG_PCI_36" to imply
> that all devices on a PAE system were able to access all of memory,
> globally removing the need for bounce buffering and allowing a native
> PCI setup for mapping memory addresses...

That would be neat.

		-ben
-- 
Fish.

  reply	other threads:[~2002-01-06  8:20 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-29 18:18 i686 SMP systems with more then 12 GB ram with 2.4.x kernel ? Harald Holzer
2001-12-29 18:45 ` Alan Cox
2001-12-29 21:24   ` M. Edward (Ed) Borasky
2001-12-30  0:25     ` M. Edward (Ed) Borasky
2001-12-30  2:14       ` Harald Holzer
2001-12-30  2:33         ` M. Edward Borasky
2002-01-01 18:15   ` M. Edward Borasky
2002-01-01 18:46     ` Alan Cox
2002-01-01 19:02       ` M. Edward Borasky
2002-01-02  1:16       ` H. Peter Anvin
2002-01-02 21:17       ` Gerrit Huizenga
2002-01-06  8:20         ` Benjamin LaHaise [this message]
2002-01-06 16:16           ` Alan Cox
2002-01-06 20:23             ` Benjamin LaHaise
2002-01-06 23:37             ` Chris Wedgwood
2002-01-07  0:29               ` The COUGAR Project M. Edward Borasky
2002-01-07  2:18               ` i686 SMP systems with more then 12 GB ram with 2.4.x kernel ? Marvin Justice
2002-01-07  2:38                 ` Chris Wedgwood
2002-01-07  4:40                   ` T. A.
2002-01-07 16:20             ` Hugh Dickins
2002-01-02 17:30 ` Timothy D. Witham
     [not found]   ` <1009994687.12942.14.camel@hh2.hhhome.at>
     [not found]     ` <1009995669.1253.17.camel@wookie-laptop.pdx.osdl.net>
2002-01-02 23:50       ` Harald Holzer
2002-01-03  0:16         ` Alan Cox
2002-01-03 13:30           ` Rik van Riel
2002-01-04 12:09             ` Hugh Dickins
2002-01-04 12:15               ` Rik van Riel
2002-01-03  0:17         ` Mark Zealey
2002-01-03 13:28         ` Rik van Riel
2002-01-03 14:33           ` Stephan von Krawczynski
2002-01-03 16:38             ` Rik van Riel
2002-01-03 15:15         ` Anton Blanchard
  -- strict thread matches above, loose matches on Subject: below --
2001-12-29 19:25 Dieter Nützel
2002-01-06 18:39 Daniel Freedman
2002-01-06 18:59 ` Marvin Justice
2002-01-06 19:45   ` Daniel Freedman
2002-01-06 20:15     ` Marvin Justice
2002-01-07  5:17       ` Daniel Freedman

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=20020106032030.A27926@redhat.com \
    --to=bcrl@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gerrit@us.ibm.com \
    --cc=harald.holzer@eunet.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=znmeb@aracnet.com \
    /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