Using dpdk-socket-mem to allocate memory for some NUMA nodes but leaving blank for subsequent ones is equivalent of assigning 0 MB memory to those subsequent nodes. Document this behavior.
Signed-off-by: Kevin Traynor <[email protected]> --- INSTALL.DPDK.md | 4 +++- vswitchd/vswitch.xml | 5 +++-- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/INSTALL.DPDK.md b/INSTALL.DPDK.md index 9ab29f3..f4d39ff 100644 --- a/INSTALL.DPDK.md +++ b/INSTALL.DPDK.md @@ -215,5 +215,7 @@ advanced install guide [INSTALL.DPDK-ADVANCED.md] * dpdk-socket-mem Comma separated list of memory to pre-allocate from hugepages on specific - sockets. + sockets. Please note when using this param for some NUMA nodes, that + subsequent NUMA nodes will be assigned 0 MB if they are not explicitly + assigned a value. * dpdk-hugepage-dir diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml index b4f2d0a..73ebef3 100644 --- a/vswitchd/vswitch.xml +++ b/vswitchd/vswitch.xml @@ -256,6 +256,7 @@ <p> The specifier is a comma-separated string, in ascending order of CPU - socket (ex: 1024,2048,4096,8192 would set socket 0 to preallocate - 1024MB, socket 1 to preallocate 2048MB, etc.) + socket. E.g. On a four socket system 1024,0,2048 would set socket 0 + to preallocate 1024MB, socket 1 to preallocate 0MB, socket 2 to + preallocate 2048MB and socket 3 (no value given) to preallocate 0MB. </p> <p> -- 1.8.3.1 _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
