[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <200710091604.50263.ak@suse.de>
Date: Tue, 9 Oct 2007 16:04:49 +0200
From: Andi Kleen <ak@...e.de>
To: "huang ying" <huang.ying.caritas@...il.com>
Cc: "Nick Piggin" <nickpiggin@...oo.com.au>,
"Huang, Ying" <ying.huang@...el.com>, linux-mm@...ck.org,
"H. Peter Anvin" <hpa@...or.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
akpm@...ux-foundation.org, "Yinghai Lu" <yhlu.kernel@...il.com>,
"Chandramouli Narayanan" <mouli@...ux.intel.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH -mm -v4 1/3] i386/x86_64 boot: setup data
On Tuesday 09 October 2007 16:00:57 huang ying wrote:
> On 10/9/07, Andi Kleen <ak@...e.de> wrote:
> >
> > > Care to add a line of documentation if you keep it in mm/memory.c?
> >
> > It would be better to just use early_ioremap() (or ioremap())
> >
> > That is how ACPI who has similar issues accessing its tables solves this.
>
> Yes. That is another solution. But there is some problem about
> early_ioremap (boot_ioremap, bt_ioremap for i386) or ioremap.
>
> - ioremap can not be used before mem_init.
> - For i386, boot_ioremap can map at most 4 pages, bt_ioremap can map
> at most 16 pages. This will be an unnecessary constrains for size of
> setup_data.
That could be easily extended if needed. But I don't see why we would
need that much setup data anyways. Limiting it to let's say 16KB
seems entirely reasonable. And if some kernel ever needs more it can
be still extended.
The biggest item is probably the command line and i don't see why
that should be more than a one or two KB.
> - For i386, the virtual memory space of ioremap is limited too.
That will be all freed and again the data shouldn't be that big.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists