public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Walrond <andrew@walrond.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Dmesg: Use a PAE enabled kernel
Date: Mon, 03 Mar 2003 16:38:58 +0000	[thread overview]
Message-ID: <3E638522.3080008@walrond.org> (raw)


The dump looks like this:

BIOS-provided physical RAM map:
   BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
   BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
   BIOS-e820: 0000000000100000 - 00000000bfffa000 (usable)
   BIOS-e820: 00000000bfffa000 - 00000000bffff000 (ACPI data)
   BIOS-e820: 00000000bffff000 - 00000000c0000000 (ACPI NVS)
   BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
   BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
   BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
   BIOS-e820: 0000000100000000 - 0000000140000000 (usable)
Warning only 4GB will be used.
Use a PAE enabled kernel.
3200MB HIGHMEM available.
896MB LOWMEM available.

So you are saying that not all the 4Gb of ram will get mapped/used
(specifically, everything not marked 'usable') ?

Can you quantify the performance degredation of a PAE enabled kernel?

Andrew Walrond




             reply	other threads:[~2003-03-03 16:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-03 16:38 Andrew Walrond [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-03 15:23 Dmesg: Use a PAE enabled kernel Andrew Walrond
2003-03-03 16:08 ` Martin J. Bligh
2003-03-03 16:24   ` Andrew Walrond
2003-03-03 16:33     ` Andrew Walrond
2003-03-03 17:42     ` Martin J. Bligh
2003-03-03 17:46     ` Alan Cox
2003-03-03 16:49       ` Andrew Walrond
2003-03-03 19:22         ` Alan Cox
2003-03-04  3:22     ` H. Peter Anvin
2003-03-03 16:54 ` Alan Cox

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=3E638522.3080008@walrond.org \
    --to=andrew@walrond.org \
    --cc=linux-kernel@vger.kernel.org \
    /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