> But more importantly than that, the whole point really is that the page
> table tree as far as Linux is concerned is nothing but an _abstraction_
> of the VM mapping hardware. It so happens that a tree format is the only
> sane format to keep full VM information that works well with real loads.
Is that still true when we get to wanting to support a full 64-bit
address space? Given that we can already tolerate losing PTEs for
resident pages from the page tables quite happily (since they can be
reconstructed from the information in the vm_area_structs and the page
cache), I don't see that the fact that a hash table will sometimes
lose PTEs because of a hash bucket filling up is all that much of a
problem. (We would need to find some other way of dealing with swap
entries of course.)
IMHO it would be interesting to compare the size and complexity of
using a hash table for the page tables with a 5-level tree. For a
32-bit address space I think the tree wins hands down but for a full
64-bit address space I am not convinced either way at present.
Paul.
-
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/