All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerrit Huizenga <gerrit@us.ibm.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: znmeb@aracnet.com (M. Edward Borasky),
	harald.holzer@eunet.at (Harald Holzer),
	linux-kernel@vger.kernel.org
Subject: Re: i686 SMP systems with more then 12 GB ram with 2.4.x kernel ?
Date: Wed, 02 Jan 2002 13:17:59 -0800	[thread overview]
Message-ID: <E16Lslt-0001aG-00@w-gerrit2> (raw)
In-Reply-To: Your message of Tue, 01 Jan 2002 18:46:40 GMT. <E16LTvs-00016I-00@the-village.bc.nu>


In message <E16LTvs-00016I-00@the-village.bc.nu>, > : Alan Cox writes:

> > 2. Isn't the boundary at 2^30 really irrelevant and the three "correct"
> > zones are (0 - 2^24-1), (2^24 - 2^32-1) and (2^32 - 2^36-1)?
> 
> Nope. The limit for directly mapped memory is 2^30.
 
The limit *per L1 Page Table Base Pointer*, that is.  You could
in theory have a different L1 Page Table base pointer for each
task (including each proc 0 in linux).  You can also pull a few
tricks such as instantiating a 4 GB kernel virtual address space
while in kernel mode (using a virtual windowing mechanism as is used
for high mem today to map in user space for copying in data from
user space if/when needed).  The latter takes some tricky code to
get mapping correct but it wasn't a lot of code in PTX.  Just needed
a lot of careful thought, review, testing, etc.

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).

> > 3. On a system without ISA DMA devices, can DMA and low be merged into a
> > single zone?
> 
> Rarely. PCI vendors are not exactly angels when it comes to implementing
> all 32bits of a DMA transfer

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...

gerrit

  parent reply	other threads:[~2002-01-06  4:08 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 [this message]
2002-01-06  8:20         ` Benjamin LaHaise
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=E16Lslt-0001aG-00@w-gerrit2 \
    --to=gerrit@us.ibm.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.