On Tue, 18 Sep 2007, Nick Piggin wrote:

quoted text
> > We can avoid all doubt in this patchset as well by adding support for
> > fallback to a vmalloced compound page.
> 
> How would you do a vmapped fallback in your patchset? How would
> you keep track of pages 2..N if they don't exist in the radix tree?

Through the vmalloc structures and through the conventions established for 
compound pages?

quoted text
> What if they don't even exist in the kernel's linear mapping? It seems
> you would also require more special casing in the fault path and special
> casing in the block layer to do this.

Well yeah there is some sucky part about vmapping things (same as in yours,
possibly more in mine since its general and not specific to the page 
cache). On the other hand a generic vcompound fallback will allow us to 
use the page allocator in many places where we currently have to use 
vmalloc because the allocations are too big. It will allow us to get rid 
of most of the vmalloc uses and thereby reduce TLB pressure somewhat.

The vcompound patchset is almost ready..... Maybe bits and pieces may 
even help fsblock.
-
unsubscribe notice
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/