[ovs-dev] [PATCH 0/2] Stop configuring '--socket-mem'/'--socket-limit' by default for DPDK if not requested.
Aaron Conole
aconole at redhat.com
Thu Jul 8 17:52:30 UTC 2021
"Rosemarie O'Riorden" <roriorde at redhat.com> writes:
> From: Rosemarie O'Riorden <roriorde at redhat.com>
>
> 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: "--scket-mem=1024,1024 --socket-limit=1024,1024"
spelling - scket should be 'socket'
I don't think it matters too much, because ovs generally doesn't do
merge commits.
> patch 1: ""
> patch 2: ""
>
> - dpdk-socket-mem=<MEM>, dpdk-socket-limit=<not set>
> current: "--scket-mem=MEM --socket-limit=MEM"
> patch 1: "--scket-mem=MEM --socket-limit=MEM"
> patch 2: "--scket-mem=MEM"
>
> - dpdk-socket-mem=<not set>, dpdk-socket-limit=<LIMIT>
> current: "--scket-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: "--scket-mem=MEM --socket-limit=LIMIT"
> patch 1: "--scket-mem=MEM --socket-limit=LIMIT"
> patch 2: "--scket-mem=MEM --socket-limit=LIMIT"
>
> Rosemarie O'Riorden (2):
> 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 | 3 +--
> NEWS | 4 ++++
> lib/dpdk.c | 6 +-----
> vswitchd/vswitch.xml | 13 ++++++-------
> 4 files changed, 12 insertions(+), 14 deletions(-)
More information about the dev
mailing list