Re: [PATCH] Document huge memory/cache overhead of memory controllerin Kconfig

[Balbir Singh]

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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/