Hi,
I looked into this once more - the data before wasn't useful as it seems it
uses internal task_set.
But I came to think this is intentional IIRC it wants to have the PMD local to
the Interface only.
So it will use the cpus on the same node as the interface, but not the others.
Could you report:
- $ numactl -H
- $ for i in /sys/bus/pci/devices/*; do printf "%s => %2s\n" $(basename $i)
$(cat $i/numa_node); done
With that we could check if that theory is true.
Perfect would be if you also have another card on another numa node, which then
only works on the other nodes cpu cores.
** Changed in: dpdk (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719392
Title:
DPDK with OVS cannot allocate CPU on different socket/processor
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1719392/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
