[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] sparse M2P table



On 16/09/2009 11:04, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:

> I'm in the process of putting together patches to eliminate undue overhead
> resulting from Xen's current assumption on a non-sparse machine address
> map. After removing large holes (symmetric across all nodes) from the
> machine address map and after also mapping the resulting (much smaller)
> frame table sparsely (to account for smaller holes distinct for one or more
> nodes), I intended to also map the P2M table sparsely.

The guest P2Ms? Why would you want to do that - so that you can add some
hierarchy (and therefore sparseness) to the pseuo-phys address space too?
Otherwise I don't see why you would ever have a sparse P2M, and therefore
why you would care about efficiently handling large holes in it.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.