[PATCH 1/2] ARM: calculate VMALLOC_END by probing inmdesc->map_io()

-----Original Message-----
From: linux-arm-kernel-bounces at lists.infradead.org [mailto:linux-
arm-kernel-bounces at lists.infradead.org] On Behalf Of Nicolas Pitre
Sent: Sunday, January 23, 2011 11:01 AM
To: Eric Miao
Cc: Russell King - ARM Linux; linux-arm-kernel at lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: calculate VMALLOC_END by probing
inmdesc->map_io()

On Sun, 23 Jan 2011, Eric Miao wrote:

quoted

On Sun, Jan 23, 2011 at 7:15 AM, Russell King - ARM Linux
[off-list ref] wrote:

quoted

I'd instead suggest adding vmalloc_end to the machine

description

quoted

quoted

record.

And since all boards sharing a same machine_class is going to use
the same value, I'd rather we first introduce struct machine_class
like in the patch I posted months ago?

Can we possibly get away with a global VMALLOC_END?  What if we were
to
decide it is fixed at 0xf0000000 for everyone?

Which would potentialy shrink the lowmem and vmalloc area. With
current flexibility of adjustable VMALLOC_END, in 1G:3G model,
we managed to  have almost ~ 896 MB virtual space available
for lowmem + vmalloc. So keeping 128MB for vmalloc ~768MB of
memory can be directly addressable without highmem support.

Regards,
Santosh