Re: [PATCH v2] x86/apic: Use smaller array for __apicid_to_node[] mapping

2015-10-09 Thread Thomas Gleixner
On Fri, 9 Oct 2015, Jiang Liu wrote: > On 2015/10/9 22:15, Thomas Gleixner wrote: > > On Mon, 5 Oct 2015, Daniel J Blueman wrote: > >> +struct apicid_to_node { > >> + int apicid; > >> + s16 node; > >> +}; > > > > Instead of having this array, why don't you use a radix tree and be > > done with i

Re: [PATCH v2] x86/apic: Use smaller array for __apicid_to_node[] mapping

2015-10-09 Thread Jiang Liu
On 2015/10/9 22:15, Thomas Gleixner wrote: > On Mon, 5 Oct 2015, Daniel J Blueman wrote: >> +struct apicid_to_node { >> +int apicid; >> +s16 node; >> +}; > > Instead of having this array, why don't you use a radix tree and be > done with it? Hi Thomas, It's in early booting stage a

Re: [PATCH v2] x86/apic: Use smaller array for __apicid_to_node[] mapping

2015-10-09 Thread Thomas Gleixner
On Mon, 5 Oct 2015, Daniel J Blueman wrote: > +struct apicid_to_node { > + int apicid; > + s16 node; > +}; Instead of having this array, why don't you use a radix tree and be done with it? Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

[PATCH v2] x86/apic: Use smaller array for __apicid_to_node[] mapping

2015-10-04 Thread Daniel J Blueman
The Intel x2APIC spec states the upper 16-bits of APIC ID is the cluster ID [1, p2-12], intended for future distributed systems. Beyond the legacy 8-bit APIC ID, Numascale NumaConnect uses 4-bits for the position of a server on each axis of a multi-dimension torus; SGI NUMAlink also structures the