Message-ID: <47BD1052.2090204@linux.vnet.ibm.com>
Date: Thu, 21 Feb 2008 11:16:58 +0530
From: Balbir Singh <balbir@linux.vnet.ibm.com>
Reply-To: balbir@linux.vnet.ibm.com
Organization: IBM
User-Agent: Thunderbird 2.0.0.9 (X11/20071115)
MIME-Version: 1.0
To: Nick Piggin <nickpiggin@yahoo.com.au>
CC: Andi Kleen <andi@firstfloor.org>, akpm@osdl.org, torvalds@osdl.org,
       linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] Document huge memory/cache overhead of memory controller
 in Kconfig
References: <20080220122338.GA4352@basil.nowhere.org> <200802211535.38932.nickpiggin@yahoo.com.au> <47BD06C2.5030602@linux.vnet.ibm.com> <200802211622.51751.nickpiggin@yahoo.com.au>
In-Reply-To: <200802211622.51751.nickpiggin@yahoo.com.au>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1253
Lines: 40

Nick Piggin wrote:
>> 1. We could create something similar to mem_map, we would need to handle 4
> 
>> different ways of creating mem_map.
> 
>> 2. On x86 with 64 GB ram, if we decided to use vmalloc space, we would need
> 
>> 64 MB of vmalloc'ed memory
> 
> That's going to be a big job. You could probably do it quite easily for
> 
> flatmem (just store an offset into the start of your page array), and
> 
> maybe even sparsemem (add some "extra" information to the extents).
> 
>> I have not explored your latest suggestion of pfn <-> memory controller
> 
>> mapping yet. I'll explore it and see how that goes.
> 
> If you did that using a radix-tree, then it could be a runtime option
> 
> without having to use vmalloc. And you wouldn't have to care about
> 
> memory models. I'd say it will be the fastest way to get a prototype
> 
> running.
> 

OK, I'll explore and prototype the radix tree based approach and see how that goes.

-- 
	Warm Regards,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/