RE: [Xen-devel] [PATCH 0/6] x86: break up post-boot non-order-ze

>>> On 06.04.11 at 04:50, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx> wrote:
> IIRC, PCI-passthrough is another user of multi-page allocations.

As noted in the description, with the intended solution being to
switch from arrays to radix trees. Or do you know of other than
the mentioned cases?

> At some point, does it make sense to eliminate the multi-page
> allocation functionality, at least through the "normal"
> page allocation routines, and add a:
> 
> /* documentation about why not to use this */
> alloc_contiguous_pages_DEPRECATED(order)
> 
> call so that it is very explicit when future page allocation
> users "regress" by adding a multi-page allocation request?

I wouldn't go that far. Instead I was considering adding a (perhaps
one-time) warning so that things wouldn't start outright failing, but
remaining code paths get pointed out. But that ought to happen
only once all known allocations have been dealt with.

Jan

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

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

[Xen-devel] RE: [PATCH][VTD] check BIOS settings before enabling interrupt remapping or x2apic, Jan Beulich

Next by Date:

[Xen-devel] Re: [PATCH][VTD] check BIOS settings before enabling interrupt remapping or x2apic, Keir Fraser

Previous by Thread:

RE: [Xen-devel] [PATCH 0/6] x86: break up post-boot non-order-zero allocations, Dan Magenheimer

Next by Thread:

[Xen-devel] [PATCH 1/6] remove direct cpumask_t members from struct vcpu and struct domain, Jan Beulich

Indexes:

[Date] [Thread] [Top] [All Lists]