linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Donald Maner <donjr@maner.org>, Raul Miller <moth@magenta.com>,
	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 00:33:39 -0500	[thread overview]
Message-ID: <3FD801B3.7080604@wmich.edu> (raw)
In-Reply-To: <3FD7FCF5.7030109@cyberone.com.au>

I thought highmem wasn't necesarily needed for memory <=2GB? Highmem 
incurs some performance hits doesn't it and so the urge to move to it 
with only 2GB is not very attractive.  Anyways i'm just interested in if 
that's the case or not since 2GB is easy to get to these days and i had 
heard that highmem could be avoided passed the 1GB barrier.



Nick Piggin wrote:
> 
> 
> Donald Maner wrote:
> 
>> The kernel you're using WAS compiled with CONFIG_HIGHMEM4G=y, correct?
>>
>> -----Original Message-----
>> From: Raul Miller [mailto:moth@magenta.com] Sent: Wednesday, December 
>> 10, 2003 10:52 PM
>> To: linux-kernel@vger.kernel.org
>> Subject: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB
>> ram.
>>
>>
>> [1.] Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.
>>
> 
> Raul Miller wrote:
> 
>>
>> [7.2.] /proc/cpuinfo says:
>>
>> processor       : 0
>> vendor_id       : AuthenticAMD
>> cpu family      : 15
>> model           : 5
>> model name      : AMD Opteron(tm) Processor 240
>>
> 
> Or ARCH=x86_64 ?
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 



  reply	other threads:[~2003-12-11  5:33 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 [this message]
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:01       ` Raul Miller
2003-12-11  6:12         ` 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
  -- strict thread matches above, loose matches on Subject: below --
2003-12-11  4:51 PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram 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=3FD801B3.7080604@wmich.edu \
    --to=ed.sweetman@wmich.edu \
    --cc=donjr@maner.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=moth@magenta.com \
    --cc=piggin@cyberone.com.au \
    /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;
as well as URLs for NNTP newsgroup(s).