Comment 0 for bug 2023578
Revision history for this message
| Giuseppe Petralia (peppepetra) wrote Make pmd-cpu-set mandatory when enable-dpdk is set | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
If pmd-cpu-set is unset, OVS DPDK will still pin the PMD threads to two cores, one per NUMA node,
that for some reasons in different envs always resulted in cpus 11 and 21
The charm should avoid this silent configuration which may lead to not properly configured systems.
i.e.
The operator may ignore that OVS will still pin the pmd threads to certain cores and may not be aware that pmd threads need to be removed from cpu-affinity range and/or nova cpu-{shared|
It would be more safe, if the charm always requires that the operator explicitly set the pmd-cpu-set when enable-dpdk is true, to force the operator thinking how cpus are assigned to the different components (OS, hypervisor, OVS dpdk).