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

Hi Tang, Your patch assumes that system supports memory less node and fixes the issue on x86 architecture. But if system does not supports memory less node, your patch cannot fix the issue. It means that system must support memory less node to support Node (CPU and memory) hotplug. Why don't

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

Hi Tang, Your patch assumes that system supports memory less node and fixes the issue on x86 architecture. But if system does not supports memory less node, your patch cannot fix the issue. It means that system must support memory less node to support Node (CPU and memory) hotplug. Why don't

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

The whole patch-set aims at solving this problem: [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

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

The whole patch-set aims at solving this problem: [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