public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jfannin@gmail.com (Joseph Fannin)
To: Tom Moore <tmoore@spatial.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 4Gb ram not showing up
Date: Tue, 5 Jun 2007 09:37:29 -0400	[thread overview]
Message-ID: <20070605133729.GA20615@nineveh.local> (raw)
In-Reply-To: <46656120.9020103@spatial.ca>

On Tue, Jun 05, 2007 at 09:12:00AM -0400, Tom Moore wrote:

> Ok, so it appears that this one is wrong also.  If someone could explain
> the rules that apply, I would be happy to prepare a patch to the Kconfig
> script.  I don't consider myself to be completely stupid, and if the
> help text was a bit more clear I wouldn't be asking these questions.
> I'm sure that other pilgrims will follow along later with the same
> questions.

   If you do create such a patch, please also state that HIGHMEM64G is
necessary for support of the NX bit (on those processors that support
it).

   ISTR that a similar issue exists in the NOHIGHMEM case, where some
150MB or so of RAM would be unusable in a 1GB machine with NOHIGHMEM.
I could be mis-remembering, that, though.

--
Joseph Fannin
jfannin@gmail.com || jhf@columbus.rr.com


  reply	other threads:[~2007-06-05 13:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-04 15:14 4Gb ram not showing up Tom Moore
2007-06-04 19:10 ` Lennart Sorensen
2007-06-04 19:45   ` Tom Moore
2007-06-04 22:28     ` Wakko Warner
2007-06-05 13:12       ` Tom Moore
2007-06-05 13:37         ` Joseph Fannin [this message]
     [not found]   ` <46646B4C.2070707@spatial.ca>
2007-06-05 18:57     ` Lennart Sorensen
2007-06-06 21:18       ` Satyam Sharma
2007-06-07  6:58         ` Jan Engelhardt
2007-06-07 13:33         ` Tom Moore
2007-06-07 20:13         ` Lennart Sorensen
2007-06-06 11:45 ` Andi Kleen

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=20070605133729.GA20615@nineveh.local \
    --to=jfannin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tmoore@spatial.ca \
    /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