Changed bug to Opinion.
I believe that: 1) charm description of the setting could point to OVS memory cacluclator at https://docs.openvswitch.org/en/latest/topics/dpdk/memory/#example-4 2) Openstack deployment guide at https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/app-ovn.html could also say word or two on this topic as it is rather terse now: ---- By default, the charm will configure Open vSwitch/DPDK to consume one processor core + 1G of RAM from each NUMA node on the unit being deployed. This can be tuned using the dpdk-socket-memory and dpdk-socket-cores configuration options. The userspace kernel driver can be configured using the dpdk-driver configuration option. See config.yaml for more details. ---- That could point to https://docs.openvswitch.org/en/latest/topics/dpdk/memory/ for dpdk-socket-memory size tuning.
Changed bug to Opinion.
I believe that: /docs.openvswit ch.org/ en/latest/ topics/ dpdk/memory/ #example- 4 /docs.openstack .org/project- deploy- guide/charm- deployment- guide/latest/ app-ovn. html could also say word or two on this topic as it is rather terse now: /docs.openvswit ch.org/ en/latest/ topics/ dpdk/memory/ for dpdk-socket-memory size tuning.
1) charm description of the setting could point to OVS memory cacluclator at https:/
2) Openstack deployment guide at https:/
----
By default, the charm will configure Open vSwitch/DPDK to consume one processor core + 1G of RAM from each NUMA node on the unit being deployed. This can be tuned using the dpdk-socket-memory and dpdk-socket-cores configuration options. The userspace kernel driver can be configured using the dpdk-driver configuration option. See config.yaml for more details.
----
That could point to https:/