Re: [PATCH 0/5] Make cpuid <-> nodeid mapping persistent.

2015-07-23 Thread Tejun Heo
Hello, Tang. On Thu, Jul 23, 2015 at 12:44:53PM +0800, Tang Chen wrote: > Allocating cpuid when a new cpu comes up and reusing the cpuid when it > comes up again is possible. But I'm not quite sure if it will be less > modification > because we still need an array or bit map or something to keep

Re: [PATCH 0/5] Make cpuid - nodeid mapping persistent.

2015-07-23 Thread Tejun Heo
Hello, Tang. On Thu, Jul 23, 2015 at 12:44:53PM +0800, Tang Chen wrote: Allocating cpuid when a new cpu comes up and reusing the cpuid when it comes up again is possible. But I'm not quite sure if it will be less modification because we still need an array or bit map or something to keep the

Re: [PATCH 0/5] Make cpuid <-> nodeid mapping persistent.

2015-07-22 Thread Tang Chen
On 07/16/2015 06:13 AM, Tejun Heo wrote: Hello, On Tue, Jul 07, 2015 at 05:30:20PM +0800, Tang Chen wrote: [Solution] To fix this problem, we establish cpuid <-> nodeid mapping for all the possible cpus at boot time, and make it invariable. And according to init_cpu_to_node(), cpuid <->

Re: [PATCH 0/5] Make cpuid - nodeid mapping persistent.

2015-07-22 Thread Tang Chen
On 07/16/2015 06:13 AM, Tejun Heo wrote: Hello, On Tue, Jul 07, 2015 at 05:30:20PM +0800, Tang Chen wrote: [Solution] To fix this problem, we establish cpuid - nodeid mapping for all the possible cpus at boot time, and make it invariable. And according to init_cpu_to_node(), cpuid - nodeid

Re: [PATCH 0/5] Make cpuid <-> nodeid mapping persistent.

2015-07-15 Thread Tejun Heo
Hello, On Tue, Jul 07, 2015 at 05:30:20PM +0800, Tang Chen wrote: > [Solution] > > To fix this problem, we establish cpuid <-> nodeid mapping for all the > possible > cpus at boot time, and make it invariable. And according to > init_cpu_to_node(), > cpuid <-> nodeid mapping is based on apicid

Re: [PATCH 0/5] Make cpuid - nodeid mapping persistent.

2015-07-15 Thread Tejun Heo
Hello, On Tue, Jul 07, 2015 at 05:30:20PM +0800, Tang Chen wrote: [Solution] To fix this problem, we establish cpuid - nodeid mapping for all the possible cpus at boot time, and make it invariable. And according to init_cpu_to_node(), cpuid - nodeid mapping is based on apicid - nodeid

[PATCH 0/5] Make cpuid <-> nodeid mapping persistent.

2015-07-07 Thread Tang Chen
[Problem] cpuid <-> nodeid mapping is firstly established at boot time. And workqueue caches the mapping in wq_numa_possible_cpumask in wq_numa_init() at boot time. When doing node online/offline, cpuid <-> nodeid mapping is established/destroyed, which means, cpuid <-> nodeid mapping will

[PATCH 0/5] Make cpuid - nodeid mapping persistent.

2015-07-07 Thread Tang Chen
[Problem] cpuid - nodeid mapping is firstly established at boot time. And workqueue caches the mapping in wq_numa_possible_cpumask in wq_numa_init() at boot time. When doing node online/offline, cpuid - nodeid mapping is established/destroyed, which means, cpuid - nodeid mapping will change if