mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Freedman <freedman@ccmr.cornell.edu>
To: 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 13:39:39 -0500	[thread overview]
Message-ID: <20020106133939.A6408@ccmr.cornell.edu> (raw)


On Jan 01 2002, H. Peter Anvin (hpa@zytor.com) wrote:
> By author: Alan Cox <alan@lxorguk.ukuu.org.uk>
> >
> > > 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.
> >
> 
> 2^30-2^27 to be exact (assuming a 3:1 split and 128MB vmalloc zone.)
> 
>         -hpa

For my better understanding, where's the 128MB vmalloc zone assumption
defined, please?

I'm pretty sure I understand that the 3:1 split you refer to is
defined by PAGE_OFFSET in asm-i386/page.h

But when I tried to find the answer in the source for the vmalloc
zone, I looked in linux/mm.h, linux/mmzone.h, linux/vmalloc.h, and
mm/vmalloc.c, but couldn't find anything there or in O'Reilly's kernel
book that I could follow/understand.

Thanks for any pointers.

Take care,

Daniel

-- 
Daniel A. Freedman
Laboratory for Atomic and Solid State Physics
Department of Physics
Cornell University

             reply	other threads:[~2002-01-06 18:40 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-06 18:39 Daniel Freedman [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2001-12-29 19:25 Dieter Nützel
     [not found] <1009995669.1253.17.camel@wookie-laptop.pdx.osdl.net>
2001-12-29 18:18 ` 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
2002-01-06 16:16             ` Alan Cox
2002-01-06 20:23               ` Benjamin LaHaise
2002-01-06 23:37               ` Chris Wedgwood
2002-01-07  2:18                 ` 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>
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

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=20020106133939.A6408@ccmr.cornell.edu \
    --to=freedman@ccmr.cornell.edu \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®