From: Zlatko Calusic <zlatko@iskon.hr>
To: Linux MM mailing list <linux-mm@kvack.org>
Subject: Re: Tell me about ZONE_DMA
Date: 06 Jul 2000 22:03:43 +0200 [thread overview]
Message-ID: <87ya3fjaao.fsf@atlas.iskon.hr> (raw)
In-Reply-To: Timur Tabi's message of "Wed, 05 Jul 2000 16:13:52 -0500"
Timur Tabi <ttabi@interactivesi.com> writes:
> I'm trying to understand the differences between the three zones, ZONE_DMA,
> ZONE_NORMAL,and ZONE_HIGHMEM. I've searched the source code (I'm getting pretty
> good at understanding the kernel memory allocator), but I can't figure out what
> physical regions of memory belong to each zone. Where is that determined?
>
First, let's assume we're talking here about i386 architecture,
because I know nothing about other architectures.
ZONE_DMA is lower 16MB of physical memory. It is special because ISA
cards can do DMA only to this part of memory.
ZONE_NORMAL is a memory that is mapped in address space of the CPU. We
use 3:1 GB split of the CPU address space. Lower 3GB is user memory,
upper 1GB is kernel and also whole physical memory has to be mapped
there (modulo vmalloc area, not very relevant for the discussion).
With 1GB of physical memory or more, extra memory above ~960MB is in
ZONE_HIGHMEM. Somebody else will explain this memory area better, so I
won't bother writing wrong facts. I haven't investigated high memory
very much.
> Also, I get this eerie feeling that it's possible for a physical page to exist
> in more than one zone. Is that true?
>
No. Every physical page is in exactly one zone, depending on its
address, see above.
Hope it helps.
--
Zlatko
--
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.eu.org/Linux-MM/
prev parent reply other threads:[~2000-07-06 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-05 21:13 Timur Tabi
2000-07-06 20:03 ` Zlatko Calusic [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=87ya3fjaao.fsf@atlas.iskon.hr \
--to=zlatko@iskon.hr \
--cc=linux-mm@kvack.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