mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Helge Hafting <helge.hafting@aitel.hist.no>
To: yogeshwar sonawane <yogyas@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: How much kernel memory is in 64-bit OS ?
Date: Mon, 18 Sep 2006 15:39:36 +0200	[thread overview]
Message-ID: <450EA198.5060302@aitel.hist.no> (raw)
In-Reply-To: <b681c62b0609180251m79071e59oe212b1133bf6944c@mail.gmail.com>

yogeshwar sonawane wrote:
> On 9/16/06, yogeshwar sonawane <yogyas@gmail.com> wrote:
>> Hi all,
>>
>> We all know that in 32-bit OS, total 4GB memory space is divided in
>> 3(user) + 1(kernel) space.
>>
>> Similarly, what is the division/scenario in case of 64-bit OS ?
>>
>> Any reference/explanation will be helpful.
>>
>> thanks in advance.
>>
>>
>> Yogeshwar
>>
>
> On similar lines, some time back, i read that, to accomodate large
> physical memory ,
> the 3G/1G layout is modified to have 4G/4G partition. But if somebody
> can focus the light on following things, it will be helpful.
> 1) what was the requirement of 4G/4G layout ?
It offers more memory than 3G/1G.  This is an improvement, so of
course it is the chosen way. It was not required - you sure can use
a 3G/1G split on a 64-bit processor - but why introduce an artifical
limitation?

The requirement for using a 4G/4G split is to have a processor
that support 64-bit adressing as well as 32-bit backward compatibility.
> 2) how it is managed ?
The kernel runs in 64-bit mode, offering the 4G/4G stuff for 32-bit 
processes.

> 3) how HIGH_MEMORY concept is related here.
high memory is a quirky way of supporting more than 4G on a 32-bit
processor.  A 64-bit processor support much more than 4G, so no need
for tricks that work around the limitations of 32-bit processors.


Helge Hafting

  reply	other threads:[~2006-09-18 13:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-16 11:34 yogeshwar sonawane
2006-09-18  0:10 ` Rik van Riel
2006-09-18  8:31   ` Andi Kleen
2006-09-18  8:35   ` Jan Engelhardt
2006-09-18 12:30     ` Rik van Riel
2006-09-18 12:34       ` Jan Engelhardt
2006-09-18 13:30         ` Kyle Moffett
2006-09-18  9:51 ` yogeshwar sonawane
2006-09-18 13:39   ` Helge Hafting [this message]
2006-09-18 17:22     ` Andi Kleen

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=450EA198.5060302@aitel.hist.no \
    --to=helge.hafting@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yogyas@gmail.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

all inboxes | Powered by JetHome®