Currently, there is a default value of 1024 for socket-mem if not configured. socket-limit automatically takes on the value of socket-mem unless otherwise specified. With these changes, memory allocation will be dynamically managed by DPDK, meaning that by default, no memory will be pre-allocated on startup, and there will be no limit to how much memory can be used. Either or both of these values can be set by the user.
The EAL arguments will look like this: - dpdk-socket-mem=<not set>, dpdk-socket-limit=<not set> current: "--socket-mem=1024,1024 --socket-limit=1024,1024" patch 1: "" patch 2: "" - dpdk-socket-mem=<MEM>, dpdk-socket-limit=<not set> current: "--socket-mem=MEM --socket-limit=MEM" patch 1: "--socket-mem=MEM --socket-limit=MEM" patch 2: "--socket-mem=MEM" - dpdk-socket-mem=<not set>, dpdk-socket-limit=<LIMIT> current: "--socket-mem=1024,1024 --socket-limit=LIMIT" patch 1: "--socket-limit=LIMIT" patch 2: "--socket-limit=LIMIT" - dpdk-socket-mem=<MEM>, dpdk-socket-limit=<LIMIT> current: "--socket-mem=MEM --socket-limit=LIMIT" patch 1: "--socket-mem=MEM --socket-limit=LIMIT" patch 2: "--socket-mem=MEM --socket-limit=LIMIT" Reported at: https://bugzilla.redhat.com/show_bug.cgi?id=1949850 Rosemarie O'Riorden (3): dpdk: Logs to announce removal of defaults for socket-mem and limit. dpdk: Remove default values for socket-mem and limit. dpdk: Stop configuring socket-limit with the value of socket-mem. Documentation/intro/install/dpdk.rst | 4 +- NEWS | 4 ++ lib/dpdk.c | 70 +--------------------------- vswitchd/vswitch.xml | 18 +++---- 4 files changed, 16 insertions(+), 80 deletions(-) -- 2.31.1 _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev