> That was my thinking earlier too, but shouldn't we have uniformity in > behaviour between kmalloc_node and alloc_pages_node wrt nodeid handling? > IMHO it would be less confusing that way. alloc_pages_node is not that much > of a fastpath routine anyways... No strong opinion either way. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- pcibus_to_node value when no pxm info is present for the pci bus
- From: Ravikiran G Thirumalai <[email protected]>
- Re: pcibus_to_node value when no pxm info is present for the pci bus
- From: Christoph Lameter <[email protected]>
- Re: pcibus_to_node value when no pxm info is present for the pci bus
- From: Ravikiran G Thirumalai <[email protected]>
- Re: [discuss] Re: pcibus_to_node value when no pxm info is present for the pci bus
- From: Andi Kleen <[email protected]>
- Re: [discuss] Re: pcibus_to_node value when no pxm info is present for the pci bus
- From: Ravikiran G Thirumalai <[email protected]>
- pcibus_to_node value when no pxm info is present for the pci bus
- Prev by Date: Re: [ACPI] ACPI owner_id limit too low
- Next by Date: Re: AW: Re: Linux in a binary world... a doomsday scenario
- Previous by thread: Re: [discuss] Re: pcibus_to_node value when no pxm info is present for the pci bus
- Next by thread: Re: [discuss] Re: pcibus_to_node value when no pxm info is present for the pci bus
- Index(es):
 |