[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20071113.173009.247667472.davem@davemloft.net>
Date: Tue, 13 Nov 2007 17:30:09 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: clameter@....com
Cc: akpm@...ux-foundation.org, linux-mm@...r.kernel.org,
linux-kernel@...r.kernel.org, dada1@...mosbay.com,
schwidefsky@...ibm.com
Subject: Re: [patch 01/28] cpu alloc: The allocator
From: Christoph Lameter <clameter@....com>
Date: Tue, 13 Nov 2007 13:40:19 -0800 (PST)
> On Tue, 13 Nov 2007, David Miller wrote:
>
> > One thing you could do is simply use a vmalloc allocation in the
> > non-virtualized case.
>
> Yuck. Meaning to add more crappy code. The bss limitations to 8M is a bit
> strange though. Do other platforms have the same issues?
sparc32 has the same limit.
I'm surprised this is your reaction instead of "oh damn, sorry
I bloated up the kernel image size by 8mb, I'll find a way to
fix that."
-
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