All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rajendra <rpm@solidcore.com>
Cc: kernelnewbies <kernelnewbies@nl.linux.org>, linux-newbie@vger.kernel.org
Subject: Re: Why "high memory" in x86?
Date: Tue, 01 Aug 2006 14:48:46 +0530	[thread overview]
Message-ID: <44CF1C76.5060406@solidcore.com> (raw)
In-Reply-To: <b115cb5f0607312248p6e05f2f2je8c6a352f7856a9a@mail.gmail.com>

The reason for the high memory is this.

   o Linux divides the address space into two parts, user and kernel.
   o Kernel gets 1 GB of address space while user gets 3GB virtual 
address space.
   o Kernel needs to access all of the  memory so ideally it needs 4 GB 
of virtual addresses.
   o But since only 1 GB (i.e. beyond 0xc000 0000) is available, so we 
call the rest as
      high memory (approx 3 GB)
   o The high memory is accessed using temp. page table entries that map 
the high memory
      areas in kernel address space.
   o The high memory region is mostly allocated to the user space programs.
  
hope it answers the question !

regd,
~rpm
Rajat Jain wrote:

> Hi list,
>
> I recently read that the concept of "High Memory" was introduced
> because certain architectures are capable of physically addressing
> larger amounts of memory than they can virtually address (physical
> address space > virtual address space). I also read that nowadays
> "high Memory" exists only in x86.
>
> 1) Why is virtual memory > 896 MB on x86 designated as high memory?
> AFAIK x86 has 4 GB of virtual address space (=physical address space?)
>
> 2) Has the "high Memory" concept got anything to do with PAE (Page
> Address Extention) feature of x86?
>
> 3) Do any other architectures than x86 have the concept of high memory?
>
> TIA,
>
> Rajat
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-newbie" 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.linux-learn.org/faqs
>

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" 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.linux-learn.org/faqs

  reply	other threads:[~2006-08-01  9:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-01  5:48 Why "high memory" in x86? Rajat Jain
2006-08-01  9:18 ` Rajendra [this message]
2006-08-01 13:51   ` Dave B. Sharp
2006-08-02  4:25     ` Rajendra
2006-08-02 16:37       ` Ritesh Kumar
2006-08-03  5:20         ` Rajendra
2006-08-03  5:59           ` Rajat Jain
2006-08-03 10:52             ` Rajendra
2006-08-03 11:55               ` Daniel Rodrick
2006-08-03 18:44                 ` Rahul Iyer
2006-08-03  6:35           ` Ritesh Kumar
     [not found] ` <20060801090248.4aad8a39@thomas.toulouse>
2006-08-01  9:53   ` Rajat Jain
2006-08-01 12:09     ` Rajat Jain

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=44CF1C76.5060406@solidcore.com \
    --to=rpm@solidcore.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-newbie@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.