mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: "Mukund JB." <mukundjb@esntechnologies.co.in>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Support for HIGHMEM ...can any one explain my Q&A ..
Date: 23 Aug 2004 08:29:28 -0600	[thread overview]
Message-ID: <m18yc6x707.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <4EE0CBA31942E547B99B3D4BFAB348110B1385@mail.esn.co.in>

"Mukund JB." <mukundjb@esntechnologies.co.in> writes:

> Hi all,
> Sorry if I asked any thing that basic level stuff?
> This is the paasge I found in the net while surfing for details about
> HIGHMEM stuff.
> 
> During 2.3 kernel development (I think), "HIGHMEM" support was added.
> Normally, the kernel can only address (4GB-PAGE_OFFSET)/PAGE_SIZE pages
> of RAM, since all physical pages must be mapped to kernel addresses
> between PAGE_OFFSET and 4GB. (So if PAGE_OFFSET is 3GB, only 1GB of
> physical RAM can be used - not even that, in practice, due to fixed
> kernel mappings and so forth.) The HIGHMEM patches allow the kernel to
> use more than 1G of memory by mapping the additional pages into the high
> part of the kernel address space just below 4GB as necessary. They also
> allow high-memory pages to be mapped into user process address space.
> 
> 
> ***) Does the above passage mean that PAGE_OFFSET is the starting
> address of my RAM ?

No.  PAGE_OFFSET is the virtual address at which physical address
0 is mapped into an arch/i386 kernel.  

> I understood so from the below line
> "since all physical pages must be mapped to kernel addresses between
> PAGE_OFFSET and 4GB".
> 
> ***) Does it mean that the lowest portion of the 4GB os nothing but RAM
> ?

No.  0-PAGE_OFFSET is the virtual address space provided to user space.
So it has an arbitrary mapping to virtual memory.

Eric

  reply	other threads:[~2004-08-23 14:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-23 13:51 Mukund JB.
2004-08-23 14:29 ` Eric W. Biederman [this message]
2004-08-24  4:10 Mukund JB.
2004-08-24  4:54 ` Dave Hansen

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=m18yc6x707.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mukundjb@esntechnologies.co.in \
    /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

Powered by JetHome