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

On Thursday, February 18, 2016 10:01:29 AM Zhu Guihua wrote: > Hi Rafael, > > On 02/03/2016 08:02 PM, Rafael J. Wysocki wrote: > > Hi, > > > > On Wed, Feb 3, 2016 at 10:14 AM, Zhu Guihua > > wrote: > >> On 01/25/2016 02:12 PM, Tang Chen wrote: > >>> Hi Rafael, Len, >

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

On Thursday, February 18, 2016 10:01:29 AM Zhu Guihua wrote: > Hi Rafael, > > On 02/03/2016 08:02 PM, Rafael J. Wysocki wrote: > > Hi, > > > > On Wed, Feb 3, 2016 at 10:14 AM, Zhu Guihua > > wrote: > >> On 01/25/2016 02:12 PM, Tang Chen wrote: > >>> Hi Rafael, Len, > >>> > >>> Would you please

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

Hi Rafael, On 02/03/2016 08:02 PM, Rafael J. Wysocki wrote: Hi, On Wed, Feb 3, 2016 at 10:14 AM, Zhu Guihua wrote: On 01/25/2016 02:12 PM, Tang Chen wrote: Hi Rafael, Len, Would you please help to review the ACPI part of this patch-set ? Can anyone help to

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

Hi Rafael, On 02/03/2016 08:02 PM, Rafael J. Wysocki wrote: Hi, On Wed, Feb 3, 2016 at 10:14 AM, Zhu Guihua wrote: On 01/25/2016 02:12 PM, Tang Chen wrote: Hi Rafael, Len, Would you please help to review the ACPI part of this patch-set ? Can anyone help to review this? I'm planning to

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

Hello, This also made workqueue blow up when delayed modding races cpu offlining. http://lkml.kernel.org/g/1454424264.11183.46.ca...@gmail.com I'll work around it from the queueing path but it'd be great if the mapping can be made stable sooner than later. Thanks. -- tejun

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

Hi, On Wed, Feb 3, 2016 at 10:14 AM, Zhu Guihua wrote: > > On 01/25/2016 02:12 PM, Tang Chen wrote: >> >> Hi Rafael, Len, >> >> Would you please help to review the ACPI part of this patch-set ? > > > Can anyone help to review this? I'm planning to look into this more thoroughly in the next few

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

On 01/25/2016 02:12 PM, Tang Chen wrote: Hi Rafael, Len, Would you please help to review the ACPI part of this patch-set ? Can anyone help to review this? Cc tj: Can you add acked-by into this patchset? Thanks. Thanks. On 01/25/2016 02:08 PM, Tang Chen wrote: [Problem] cpuid <->

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

On 01/25/2016 02:12 PM, Tang Chen wrote: Hi Rafael, Len, Would you please help to review the ACPI part of this patch-set ? Can anyone help to review this? Cc tj: Can you add acked-by into this patchset? Thanks. Thanks. On 01/25/2016 02:08 PM, Tang Chen wrote: [Problem] cpuid <->

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

Hi, On Wed, Feb 3, 2016 at 10:14 AM, Zhu Guihua wrote: > > On 01/25/2016 02:12 PM, Tang Chen wrote: >> >> Hi Rafael, Len, >> >> Would you please help to review the ACPI part of this patch-set ? > > > Can anyone help to review this? I'm planning to look into this more

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

Hello, This also made workqueue blow up when delayed modding races cpu offlining. http://lkml.kernel.org/g/1454424264.11183.46.ca...@gmail.com I'll work around it from the queueing path but it'd be great if the mapping can be made stable sooner than later. Thanks. -- tejun

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

Hi Rafael, Len, Would you please help to review the ACPI part of this patch-set ? Thanks. On 01/25/2016 02:08 PM, Tang Chen wrote: [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

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

[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 v5 RESEND 0/5] Make cpuid <-> nodeid mapping persistent

[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

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

Hi Rafael, Len, Would you please help to review the ACPI part of this patch-set ? Thanks. On 01/25/2016 02:08 PM, Tang Chen wrote: [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