All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Golds <jgolds@resilience.com>
To: Rik van Riel <riel@conectiva.com.br>,
	Wayne Whitney <whitney@math.berkeley.edu>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.4.4 kernel reports wrong amount of physical memory
Date: Mon, 14 May 2001 16:41:16 -0700	[thread overview]
Message-ID: <3B006D1C.CFBD1CC8@resilience.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0105142025000.18102-100000@duckman.distro.conectiva> <3B006CC7.AAD065BA@resilience.com>

Jeff Golds wrote:
> 
> Rik van Riel wrote:
> >
> > On Mon, 14 May 2001, Wayne Whitney wrote:
> > > In mailing-lists.linux-kernel, you wrote:
> > >
> > > > You need to compile highmem support into the kernel if you want to
> > > > use more than 890 MB of RAM, set it to maximum 4GB for best
> > > > performance...
> > >
> > > On a similar note, what is the maximum physical memory supported
> > > by the 4GB option?
> >
> > Ummm, 4GB maybe? ;)
> >
> > Rik
> 
> Ahh, it's totally obvious.  1 GB option = 890 MB, 4 GB option = 4GB.  Can I assume a linear relation and get 66.2 MB when I select the 64 MB option?
> 
> ;)
> 
> -Jeff
> 

That's GB not MB =P

-Jeff


-- 
Jeff Golds
jgolds@resilience.com

  reply	other threads:[~2001-05-14 23:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-14 19:09 2.4.4 kernel reports wrong amount of physical memory Jeff Golds
2001-05-14 19:29 ` Alan Cox
2001-05-14 20:01 ` Rik van Riel
2001-05-14 22:50   ` Wayne Whitney
2001-05-14 23:25     ` Rik van Riel
2001-05-14 23:39       ` Jeff Golds
2001-05-14 23:41         ` Jeff Golds [this message]
2001-05-15  0:44         ` Rik van Riel
2001-05-15  1:00           ` Mohammad A. Haque
2001-05-15  1:07           ` Jeff Golds
2001-05-15  2:32             ` Rik van Riel
2001-05-15  4:19               ` [PATCH] " Wayne Whitney
2001-05-15  0:25       ` H. Peter Anvin
2001-05-15  1:57         ` Brian Gerst
2001-05-15  1:46           ` H. Peter Anvin

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=3B006D1C.CFBD1CC8@resilience.com \
    --to=jgolds@resilience.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=whitney@math.berkeley.edu \
    /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.