dpdk-socket-cores misleading description
Bug #1905284 reported by
Michał Ajduk
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Neutron Open vSwitch Charm |
Fix Released
|
Medium
|
Chris MacNaughton | ||
charm-ovn-chassis |
Fix Released
|
Medium
|
Unassigned |
Bug Description
As per the description of the config option:
dpdk-socket-cores:
(int) Number of cores to allocate to DPDK per NUMA socket in deployed systems. . Only used when DPDK is enabled.
System has 2 NUMA nodes:
NUMA node0 CPU(s): 0-19,40-59
NUMA node1 CPU(s): 20-39,60-79
Only one thread is allocated to PMD driver instead of expected 2 - consult attached htop screenshot.
Changed in charm-ovn-chassis: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in charm-neutron-openvswitch: | |
milestone: | none → 21.10 |
Changed in charm-neutron-openvswitch: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
ubuntu@ inf1az1cz202904 rz:~/deploy$ juju config ovn-chassis-dpdk dpdk-socket-cores
1
This renders following config on the machine: 0300kvd: ~# ovs-vsctl get Open_vSwitch . other_config: dpdk-lcore- mask
root@cmp3az1cz2
"0x100001"
dpdk-lcore-mask
Specifies the CPU cores on which dpdk lcore threads should be spawned and expects hex string (eg ‘0x123’).
root@cmp3az1cz2 0300kvd: ~# ovs-vsctl get Open_vSwitch . other_config: pmd-cpu- mask
ovs-vsctl: no key "pmd-cpu-mask" in Open_vSwitch record "." column other_config
That contains 2 CPUs:
1
1048576 mod 80 = 16
I'm not usre how this maps to PMD core 12 that is actually in use