Re: [ovs-dev] [PATCH v2 1/2] ovs-numa: Non-consecutively numa nodes and cores

2020-02-06 Thread dwilder
On 2020-02-06 12:58, Ben Pfaff wrote: On Thu, Feb 06, 2020 at 12:38:16PM -0800, David Wilder wrote: +char *path; + +path = xasprintf( "/sys/devices/system/cpu/cpu%d/topology/core_id" , + core_id); +if (access(path, F_OK) != 0) { +return 0; } + +

Re: [ovs-dev] [PATCH v2 1/2] ovs-numa: Non-consecutively numa nodes and cores

2020-02-06 Thread Ben Pfaff
On Thu, Feb 06, 2020 at 12:38:16PM -0800, David Wilder wrote: > +char *path; > + > +path = xasprintf( "/sys/devices/system/cpu/cpu%d/topology/core_id" , > + core_id); > +if (access(path, F_OK) != 0) { > +return 0; > } > + > +return 1; I didn't read

[ovs-dev] [PATCH v2 1/2] ovs-numa: Non-consecutively numa nodes and cores

2020-02-06 Thread David Wilder
This change removes the assumption that numa nodes and cores are numbered consecutively in linux. This change is required to support some Power systems. An additional check has been added to verify that cores are online, offline cores result in non-consecutively numbered cores. I manually