public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: Raul Miller <moth@magenta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.
Date: Thu, 11 Dec 2003 17:12:07 +1100	[thread overview]
Message-ID: <3FD80AB7.3010909@cyberone.com.au> (raw)
In-Reply-To: <20031211010132.F28449@links.magenta.com>



Raul Miller wrote:

>On Wed, Dec 10, 2003 at 11:06:46PM -0600, Donald Maner wrote:
>
>>The kernel you're using WAS compiled with CONFIG_HIGHMEM4G=y, correct?
>>
>
>No.
>
>
>On Thu, Dec 11, 2003 at 04:13:25PM +1100, Nick Piggin wrote:
>
>>Or ARCH=x86_64 ?
>>
>
>Yes.  Well, no... I don't see that option in my .config.  I
>did specify the amd64 bit archictecture, but I don't know
>what that means in .config terms.  Here's what's set under
>"# Processor type and features":
>

This optimises the kernel for your chip when its in 32-bit mode.
make 'ARCH=x64_64' to make a 64-bit kernel, however you would
need a cross compiler.

>
>On Thu, Dec 11, 2003 at 04:48:51PM +1100, Nick Piggin wrote:
>
>>At any rate, Raul, highmem shouldn't hurt your performance significantly
>>with the 2.6 kernel. If it does then send a note to the list.
>>
>
>Ok, I guess I'll try that (tomorrow, unless I hear any better suggestions
>before then).
>
>[I thought highmem was something completely different -- that it declared
>a watermark and memory above that watermark was treated differently.
>However, I guess I understand that this might have the side effect of
>bumping things around such that I get access to the memory.]
>

No you're right, but the kernel tries not to use highmem for data it
accesses a lot. cache and anonymous memory for example.



  reply	other threads:[~2003-12-11  6:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-11  5:06 PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram Donald Maner
2003-12-11  5:13 ` Nick Piggin
2003-12-11  5:33   ` Ed Sweetman
2003-12-11  5:41     ` William Lee Irwin III
2003-12-11  5:48       ` Roland Dreier
2003-12-11  5:50         ` William Lee Irwin III
2003-12-11  5:48       ` Nick Piggin
2003-12-11  6:30       ` David Lang
2003-12-11  7:08       ` Martin J. Bligh
2003-12-11  7:19         ` William Lee Irwin III
2003-12-11  7:22           ` Martin J. Bligh
2003-12-11 13:24         ` William Lee Irwin III
2003-12-11 14:41       ` Raul Miller
2003-12-11 14:53         ` Raul Miller
2003-12-11 15:00         ` William Lee Irwin III
2003-12-11 16:17           ` moth
2003-12-11 16:35             ` William Lee Irwin III
2003-12-11 19:26           ` Where did the ELF spec go? (SCO website?) Rob Landley
2003-12-11 19:44             ` William Lee Irwin III
2003-12-11 20:25               ` Richard B. Johnson
2003-12-12 11:11                 ` Johannes Stezenbach
2003-12-11  6:01 ` PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram Raul Miller
2003-12-11  6:12   ` Nick Piggin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-11  4:51 Raul Miller

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=3FD80AB7.3010909@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=moth@magenta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox