lkml.org 
[lkml]   [2008]   [Sep]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
Date
From
SubjectRe: wrong usage of MAX_DMA_ADDRESS in bootmem.h
On Tue, 30 Sep 2008, Russell King - ARM Linux wrote:

> As we have already covered in the past, CONFIG_ZONE_DMA has to always
> be enabled on ARM because ARM always puts all memory in the first zone.
> To do otherwise introduces lots of special cases, and I steadfastly
> refuse to make the memory initialisation any more complicated than it
> already is.

I just tried this:

diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 70dba16..8f609cc 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -148,7 +148,6 @@ config ARCH_MAY_HAVE_PC_FDC

config ZONE_DMA
bool
- default y

config GENERIC_ISA_DMA
bool
with no other changes what so ever. And the resulting kernel still
works fine, with this difference:

|On node 0 totalpages: 131072
|free_area_init_node: node 0, pgdat c03c5e00, node_mem_map c03e7000
| Normal zone: 130048 pages, LIFO batch:31

instead of:

|On node 0 totalpages: 131072
|free_area_init_node: node 0, pgdat c03c7e58, node_mem_map c03e9000
| DMA zone: 130048 pages, LIFO batch:31

And the resulting kernel is also smaller:

| text data bss dec hex filename
|3826182 102384 111700 4040266 3da64a vmlinux
|3823593 101616 111700 4036909 3d992d vmlinux.nodmazone

So maybe CONFIG_DMA_ZONE could be selected only by those machines
actually defining arch_adjust_zones() ?

> And besides, this has nothing to do with that issue.

Indeed. But still...


Nicolas


\
 
 \ /
  Last update: 2008-09-30 23:13    [W:0.056 / U:0.748 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site