[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] Re: non-contiguous allocations
On Mon, Apr 18, Olaf Hering wrote: > On Fri, Apr 01, George Dunlap wrote: > > > On Wed, 2011-03-30 at 19:04 +0100, Olaf Hering wrote: > > > Using the u16 means each cpu could in theory use up to 256MB as trace > > > buffer. However such a large allocation will currently fail on x86 due > > > to the MAX_ORDER limit. > > > > FWIW, I don't believe that there's any reason the allocations have to be > > contiguous any more. I kept them contiguous to minimize the changes to > > the moving parts near a release. But the new system has been pretty > > well tested now, so I think looking at non-contiguous allocations may be > > worthwhile. Is there a way to allocate more than 128mb with repeated calls to alloc_xenheap_page()? From which pool should the per-cpu tracebuffers get allocated? alloc_domheap_page() wants a domain, so I think thats the wrong interface. Olaf _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |