The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Mark de Vries <m.devries@nl.tiscali.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 1GB, highmem or no?
Date: 18 Sep 2003 00:28:29 +0200	[thread overview]
Message-ID: <m3k7876odu.fsf@defiant.pm.waw.pl> (raw)
In-Reply-To: <3F68B0EE.1@nl.tiscali.com>

Mark de Vries <m.devries@nl.tiscali.com> writes:

> I recently added some memory and now have 1GB and the kernel tells me:
> "Warning only 896MB will be used.
> Use a HIGHMEM enabled kernel.
> 896MB LOWMEM available."
> 
> So I'm not using ~128MB of my memory...
> 
> My question is: is enableling HIGHMEM worth it?

You may consider using a different split as well. I'm using 2 GB : 2 GB
split with 1 GB of RAM with no need for highmem.

BTW: Is it really safe to use something like 2.5 GB : 1.5 GB user/kernel
scheme? I don't want PAE nor HIGHMEM.
-- 
Krzysztof Halasa, B*FH

      reply	other threads:[~2003-09-18 10:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-17 19:07 1GB, highmem or no? Mark de Vries
2003-09-17 22:28 ` Krzysztof Halasa [this message]

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=m3k7876odu.fsf@defiant.pm.waw.pl \
    --to=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.devries@nl.tiscali.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