RFR(XS) 8181055: "mbind: Invalid argument" still seen after 8175813

[Zhengyu Gu]

This is a quick way to kill the symptom (or low risk?). I am not sure if 
disabling NUMA is a better solution for this circumstance? does 1 NUMA 
node = UMA?

Thanks,

-Zhengyu

On 05/26/2017 09:14 AM, Zhengyu Gu wrote:
> Hi,
>
> There is a corner case that still failed after JDK-8175813.
>
> The system shows that it has multiple NUMA nodes, but only one is
> configured. Under this scenario, numa_interleave_memory() call will
> result "mbind: Invalid argument" message.
>
> Bug: https://bugs.openjdk.java.net/browse/JDK-8181055
> Webrev: http://cr.openjdk.java.net/~zgu/8181055/webrev.00/
>
>
> The system NUMA configuration:
>
> Architecture: ppc64
> CPU op-mode(s): 32-bit, 64-bit
> Byte Order: Big Endian
> CPU(s): 8
> On-line CPU(s) list: 0-7
> Thread(s) per core: 4
> Core(s) per socket: 1
> Socket(s): 2
> NUMA node(s): 2
> Model: 2.1 (pvr 003f 0201)
> Model name: POWER7 (architected), altivec supported
> L1d cache: 32K
> L1i cache: 32K
> NUMA node0 CPU(s): 0-7
> NUMA node1 CPU(s):
>
> Thanks,
>
> -Zhengyu