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: Mon, 7 Jan 2002 00:17:54 -0500 [thread overview]
Message-ID: <20020107001754.D7272@ccmr.cornell.edu> (raw)
In-Reply-To: <20020106133939.A6408@ccmr.cornell.edu> <200201061856.g06IuXma007731@sm13.texas.rr.com> <20020106144525.B6408@ccmr.cornell.edu> <200201062011.g06KBpu3007487@sm14.texas.rr.com>
In-Reply-To: <200201062011.g06KBpu3007487@sm14.texas.rr.com>; from mjustice@austin.rr.com on Sun, Jan 06, 2002 at 02:15:24PM -0600
On Sun, Jan 06, 2002, Marvin Justice wrote:
> On Sunday 06 January 2002 01:45 pm, Daniel Freedman wrote:
> > Hi Marvin,
> >
> > Thanks for the quick reply.
> >
> > On Sun, Jan 06, 2002, Marvin Justice wrote:
> > > Is this what your looking for? Just below the definition of PAGE_OFFSET
> > > in page.h:
> > >
> > > /*
> > > * This much address space is reserved for vmalloc() and iomap()
> > > * as well as fixmap mappings.
> > > */
> > > #define __VMALLOC_RESERVE (128 << 20)
> >
> > However, while it does seem to be exactly the definition for 128MB
> > vmalloc offset that I was looking for, I don't seem to have this
> > definition in my source tree (2.4.16):
> >
> > freedman@planck:/usr/src/linux$ grep -r __VMALLOC_RESERVE *
> > freedman@planck:/usr/src/linux$
>
> Hmmm. Looks like it was moved sometime between 2.4.16 and 2.4.18pre1. In my
> 2.4.16 tree it's located in arch/i386/kernel/setup.c and without the leading
> underscores.
>
> -M
<sheepishly buries head in sand> Oops... Sorry about missing that.
Thanks for the help and take care,
Daniel
--
Daniel A. Freedman
Laboratory for Atomic and Solid State Physics
Department of Physics
Cornell University
next prev parent reply other threads:[~2002-01-07 5:18 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-06 18:39 i686 SMP systems with more then 12 GB ram with 2.4.x kernel ? 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-29 19:25 Dieter Nützel
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>
[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
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=20020107001754.D7272@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