From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: calculate VMALLOC_END by probing inmdesc->map_io()
Date: Sun, 23 Jan 2011 12:45:55 +0530 [thread overview]
Message-ID: <9dbba3c432aab294761c32527bc5e96d@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1101230024240.8580@xanadu.home>
> -----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:
>
> > On Sun, Jan 23, 2011 at 7:15 AM, Russell King - ARM Linux
> > <linux@arm.linux.org.uk> wrote:
> > > I'd instead suggest adding vmalloc_end to the machine
> description
> > > 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
next prev parent reply other threads:[~2011-01-23 7:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 22:56 [PATCH 1/2] ARM: calculate VMALLOC_END by probing in mdesc->map_io() Eric Miao
2011-01-22 22:56 ` [PATCH 2/2] ARM: remove now useless vmalloc.h Eric Miao
2011-01-22 23:15 ` [PATCH 1/2] ARM: calculate VMALLOC_END by probing in mdesc->map_io() Russell King - ARM Linux
2011-01-23 4:59 ` Eric Miao
2011-01-23 5:30 ` Nicolas Pitre
2011-01-23 7:15 ` Santosh Shilimkar [this message]
2011-01-23 14:17 ` [PATCH 1/2] ARM: calculate VMALLOC_END by probing inmdesc->map_io() Nicolas Pitre
2011-01-23 14:27 ` Santosh Shilimkar
2011-01-23 9:40 ` [PATCH 1/2] ARM: calculate VMALLOC_END by probing in mdesc->map_io() Russell King - ARM Linux
2011-01-23 14:21 ` Nicolas Pitre
2011-01-23 14:34 ` Russell King - ARM Linux
2011-01-23 23:05 ` Eric Miao
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=9dbba3c432aab294761c32527bc5e96d@mail.gmail.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).