Detailed bug description:
NIC's NUMA affinity is incorrect
Steps to reproduce:
Using Machine with multiple NUMA's
1. Open Interfaces response raw data and Node mete numa_topology data
Expected results:
NIC has numa_node according to bus_info
Actual result:
NIC info: [
{
"name": "enp10s0f0",
... "interface_properties": {
... "numa_node": null,
},
"bus_info": "0000:81:00.0"
},
]
Node's numa_topology.numa_nodes info: [ { "pcidevs": [ "0000:81:00.0", "0000:81:00.1" ], "cpus": [...], "id": 2, "memory": 67644473344 },
...
]
Reproducibility:
<put your information here>
Workaround:
<put your information here>
Impact:
<put your information here>
Description of the environment:
Detailed bug description:
"interface_ properties" : {
"numa_ node": null, numa_nodes info: [
{
"pcidevs" : [
"0000:81: 00.0",
"0000:81: 00.1"
],
"cpus" : [...],
"id" : 2,
"memory" : 67644473344
} ,
NIC's NUMA affinity is incorrect
Steps to reproduce:
Using Machine with multiple NUMA's
1. Open Interfaces response raw data and Node mete numa_topology data
Expected results:
NIC has numa_node according to bus_info
Actual result:
NIC info: [
{
"name": "enp10s0f0",
...
...
},
"bus_info": "0000:81:00.0"
},
]
Node's numa_topology.
...
]
Reproducibility:
<put your information here>
Workaround:
<put your information here>
Impact:
<put your information here>
Description of the environment: