| 2023-06-12 17:42:57 |
Giuseppe Petralia |
bug |
|
|
added bug |
| 2023-06-12 17:44:11 |
Giuseppe Petralia |
description |
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|dedicated}-set.
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). |
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|dedicated}-set.
It would be safer, 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). |
|
| 2023-06-12 17:44:29 |
Giuseppe Petralia |
description |
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|dedicated}-set.
It would be safer, 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). |
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|dedicated}-set.
It would be safer, if the charm always requires that the operator explicitly sets 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). |
|
| 2023-06-12 17:44:55 |
Giuseppe Petralia |
description |
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|dedicated}-set.
It would be safer, if the charm always requires that the operator explicitly sets 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). |
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|dedicated}-set.
It would be safer, if the charm always requires that the operator explicitly sets 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). |
|
| 2023-06-12 17:47:20 |
Giuseppe Petralia |
summary |
Make pmd-cpu-set mandatory when enable-dpdk is set |
Make pmd-cpu-set mandatory when enable-dpdk is true |
|
| 2023-06-12 18:52:20 |
Andrea Ieri |
tags |
|
bseng-1276 |
|
