From: Pei Lin <telent997@gmail.com>
To: Mark Brown <markb@marksmachinations.com>
Cc: Marcos Roriz <marcosrorizinf@gmail.com>,
kernelnewbies@nl.linux.org, linux-mm@kvack.org
Subject: Re: Memory Concepts [+Newbie]
Date: Tue, 5 May 2009 14:07:31 +0800 [thread overview]
Message-ID: <41d311580905042307t75ad393eo35e9b90aa15486b2@mail.gmail.com> (raw)
In-Reply-To: <82459C1E-87E6-497C-8D09-21FD5FA5709E@marksmachinations.com>
That book << Understating the Linux Virtual Memory Manager>> clearly
elaborate why ZONE_NORMAL is 896 on the section 4.1 Linear Address
Space.
SEE the comment about ZONE_HIGHMEM, include/linux/mmzone.h
#ifdef CONFIG_HIGHMEM
/*
* A memory area that is only addressable by the kernel through
* mapping portions into its own address space. This is for example
* used by i386 to allow the kernel to address the memory beyond
* 900MB. The kernel will set up special mappings (page
* table entries on i386) for each page that the kernel needs to
* access.
*/
ZONE_HIGHMEM,
#endif
2009/5/4 Mark Brown <markb@marksmachinations.com>:
> Hi Marcos,
>
> A memory bank for RAM is just an individual addressable array on a memory
> board. The addressing of the bank is managed by the memory controller.
>
> Regards,
> -- Mark
>
> On May 4, 2009, at 7:44 AM, Marcos Roriz wrote:
>
>> I'm reading Mel Gorman Understating the Linux Virtual Memory Manager and
>> also TANENBAUM Modern Operating System I don't get some basic concepts of
>> the Memory Management in Linux Kernel.
>>
>> The first question is, what is a memory bank, It's not clear if its a
>> physical section of the memory of if its a chip (physical) itself.
>>
>> The ZONE_NORMAL zone refer only to kernel direct memory mapped, that means
>> only to kernel pages and kernel programs (such as daemons)?
>>
>> Why is the ZONE_NORMAL so large (896 MB)? How to deal with low memory
>> systems?
>>
>> The ZONE_HIGHMEM zone refer to kernel not mapped directly, so that
>> includes userspace programs right?
>>
>> I googled and searched for all those answers but couldn't find a direct
>> and consistent answer, thats why I'm asking for your guys help.
>>
>> Thanks very much for you time,
>>
>> Marcos Roriz
>>
>> --
>> To unsubscribe from this list: send an email with
>> "unsubscribe kernelnewbies" to ecartis@nl.linux.org
>> Please read the FAQ at http://kernelnewbies.org/FAQ
>>
>
>
> --
> To unsubscribe from this list: send an email with
> "unsubscribe kernelnewbies" to ecartis@nl.linux.org
> Please read the FAQ at http://kernelnewbies.org/FAQ
>
>
--
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>
next prev parent reply other threads:[~2009-05-05 6:07 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 [this message]
2009-05-05 8:05 ` 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=41d311580905042307t75ad393eo35e9b90aa15486b2@mail.gmail.com \
--to=telent997@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-mm@kvack.org \
--cc=marcosrorizinf@gmail.com \
--cc=markb@marksmachinations.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).