From: gprabhunath@gmail.com (Prabhu nath)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Basic HighMeM Question
Date: Tue, 28 Jun 2011 16:19:07 +0530 [thread overview]
Message-ID: <BANLkTimgR6kBBK4pLRKBd+quDB9Wr__G+w@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=yTsMbt51GNFKUOqCkNd7j8bRawQ@mail.gmail.com>
Dear Mulyadi,
You are always an important character to jump in to any discussion and it
will be our great pleasure.
Please see inline for my views.
On Tue, Jun 28, 2011 at 3:46 PM, Mulyadi Santosa
<mulyadi.santosa@gmail.com>wrote:
> Is it okay to jump in, guys?
>
> On Tue, Jun 28, 2011 at 12:51, piyush moghe <pmkernel@gmail.com> wrote:
> > Thanks Prabhu.
> > So does this means that this ZONE_NORMAL limit of 896MB is because of 3:1
> > memory division?
>
> partly yes, plus 896 MB itself is due to some reservation in kernel
> address space such as vmalloc, fixmap etc.
>
In a 3G/1G partition. 1G of Kernel virtual address space is divided into
896MB and 128 MB regions. I name them as
Fixed Constant Offset mapped region (FCOM) - 0xC0000000 to 0xF8000000
Dynamically Arbitrarily Mappable region (DAMR) - 0xF8000000 to 0xFFFFFFFF
FCOM region virtual address as the name depicts is already mapped to the
physical address range from 0x00000000 to 0x38000000. i.e. for any virtual
address in the FCOM region there is a readily available Physical address.
Base kernel code/data/stack and all kmalloc allocations are associated to
FCOM region virtual address which require contiguity in virtual address as
well as physical memory.
Those Device drivers code/data which are built as modules, vmalloc
allocations which need not be contiguous in memory and but only contiguous
in virtual address space will be in associated to DAMR region.
For exp. Check out the address of your kernel module functions which are
built as modules and insmoded to the kernel. it will be in DAMR region.
The kernel symbol *high_memory* will give the start kernel virtual
address of DAMR region.
If you have 512 MB of RAM and it is decoded from 0x00000000 to 0x0x20000000.
Now you have ZONE_NORMAL size of ~512 MB.
Check out the value of high_memory. You will have lot of thoughts on this
and refer ULK chapter 8.
> > If it is do then does this mean that if this ratio is changed then
> > ZONE_NORMAL limit will also be changed?
>
> see above...
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com
> training: mulyaditraining.blogspot.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110628/2f55f513/attachment.html
next prev parent reply other threads:[~2011-06-28 10:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 9:12 Basic HighMeM Question piyush moghe
2011-06-27 9:28 ` Prabhu nath
[not found] ` <BANLkTinp6_n0z6OAzo1R6sq_nLynyo_3Xg@mail.gmail.com>
2011-06-27 11:15 ` Prabhu nath
2011-06-28 5:51 ` piyush moghe
2011-06-28 10:16 ` Mulyadi Santosa
2011-06-28 10:49 ` Prabhu nath [this message]
2011-06-28 15:26 ` Mulyadi Santosa
2011-06-29 6:30 ` piyush moghe
2011-06-29 6:38 ` Mulyadi Santosa
2011-06-29 7:34 ` Paraneetharan Chandrasekaran
2011-06-29 9:03 ` Mulyadi Santosa
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=BANLkTimgR6kBBK4pLRKBd+quDB9Wr__G+w@mail.gmail.com \
--to=gprabhunath@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).