From: Mulyadi Santosa <mulyadi.santosa@gmail.com>
To: Marcos Roriz <marcosrorizinf@gmail.com>
Cc: kernelnewbies@nl.linux.org, linux-mm@kvack.org
Subject: Re: Memory Concepts [+Newbie]
Date: Tue, 5 May 2009 15:05:58 +0700 [thread overview]
Message-ID: <f284c33d0905050105r5c0d8d37l68cad8cce6ffb54d@mail.gmail.com> (raw)
In-Reply-To: <49FED524.9020602@gmail.com>
Hi...
On Mon, May 4, 2009 at 6:44 PM, Marcos Roriz <marcosrorizinf@gmail.com> wrote:
> The ZONE_NORMAL zone refer only to kernel direct memory mapped, that means
> only to kernel pages and kernel programs (such as daemons)?
as the name implies, it means a memory area where kernel can directly
address it without a need to do temporary mapping.
For the user space programs, it has somewhat loose connection. When
kernel try to serve memory request from user space, it could get free
pages from either zone normal or highmem (depending on the priority).
Once these oages are "connected " to user space via PTE (page table
entry), they are directly accessible by user space program.
> Why is the ZONE_NORMAL so large (896 MB)? How to deal with low memory
> systems?
first of all, you need to understand the default virtual memory split
for x86 32 bit system, that is 3:1. Meaning, user mode has 3 GB, while
kernel has 1 GB. Inside this 1GB address space, not all address range
can be used. Some of them are used for temporary mapping, vmalloc
mapping and so on. Short story, you're left with 896 MB address space.
For low memory system, the address space is still 1 GB. But in
reality, only a little is used to map the RAM. So in hand we have
large address space, but it doesn't mean all those addresses are used.
> The ZONE_HIGHMEM zone refer to kernel not mapped directly, so that includes
> userspace programs right?
Kindly refer to my explanations above :) Again, user space program
doesn't really care about zone normal or highmem.
regards,
Mulyadi.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2009-05-05 8:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 11:44 Memory Concepts [+Newbie] Marcos Roriz
2009-05-04 12:28 ` Mark Brown
2009-05-05 6:07 ` Pei Lin
2009-05-05 8:05 ` Mulyadi Santosa [this message]
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=f284c33d0905050105r5c0d8d37l68cad8cce6ffb54d@mail.gmail.com \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-mm@kvack.org \
--cc=marcosrorizinf@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;
as well as URLs for NNTP newsgroup(s).