Why I don't say "optimize this! now! more!" is where this is called is
limited now. only at charge/uncharge. This is not memmap.
charge ...the first page fault to the page
add to radix-tree
uncharge ...the last unmap aginst the page
remove from radix-tree.
I can make this faster by using charactoristics of FLATMEM and others.
(with more #ifdefs and codes.)
But would like to start from generic one because adding interface is
the first thing I have to do here.
BTW, to be honest, I don't like 2-level-table-lookup like
SPARSEMEM_EXTREME, here. A style like SPARSEMEM_VMEMMAP...using
linear virtual address map will be goal of mine.
Thanks,
-Kame
--