On Thu, 20 Sep 2007, Andrea Arcangeli wrote:

quoted text
> The only point of this largepage stuff is to go an extra mile to save
> a bit more of cpu vs a strict vmap based solution (fsblock of course
> will be smart enough that if it notices the PAGE_SIZE is >= blocksize
> it doesn't need to run any vmap at all and it can just use the direct
> mapping, so vmap translates in 1 branch only to check the blocksize
> variable, PAGE_SIZE is immediate in the .text at compile time). But if

Hmmm.. You are not keeping up with things? Heard of virtual compound 
pages? They only require a vmap when the page allocator fails a 
larger order allocation (which we have established is rare to the point 
of nonexistence). The next rev of large blocksize will use that for 
fallback. Plus vcompounds can be used to get rid of most uses of vmalloc 
reducing the need for virtual mapping in general.

Largeblock is a general solution for managing large data sets using a 
single page struct. See the original message that started this thread. It 
can be used for various other subsystems like vcompound can.
-
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/