Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
The FDP team is no longer accepting new bugs in Bugzilla. Please report your issues under FDP project in Jira. Thanks.

Bug 1944568

Summary: [RFE] Support dynamic hugemem memory allocation/deallocation.
Product: Red Hat Enterprise Linux Fast Datapath Reporter: Eelco Chaudron <echaudro>
Component: openvswitch2.15Assignee: Open vSwitch development team <ovs-team>
Status: CLOSED DUPLICATE QA Contact: liting <tli>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: FDP 21.ACC: ctrautma, fleitner, jhsiao, msantana, ralongi
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-07 15:15:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eelco Chaudron 2021-03-30 08:40:10 UTC
Configuring the switch huge pages is a pain. In more generic cases that could be dynamically managed by vswitchd.

Comment 1 Michael Santana 2021-06-22 13:20:48 UTC
Adding an update to provide more context on this

When setting up OVS with DPDK one can pass an optional flag `dpdk-socket-mem` [1] to determine the amount of hugepage memory to allocate via DPDK.
If the flag is omitted then 1gb of memory will be preallocated (by DPDK) with no option to request more. The only option to request more would be by restarting OVS and increasing the value of dpdk-socket-mem.
Which leaves the admin running ovs with no choice but to know how much memory their application will use in advanced, or risk having to restart OVS if this number is too low.
A much better solution is to let DPDK dynamically allocate it's own memory at run time. DPDK already supports dynamic memory allocation by default [2] which is what this bugzilla is proposing to use.

We think that internally OVS translates the argument passed via the flag dpdk-socket-mem to something DPDK understands [2] using --socket-mem which makes another bugzilla [3] a close duplicate of this one



[1] - https://github.com/openvswitch/ovs/blob/master/Documentation/intro/install/dpdk.rst#setup-ovs
[2] - https://doc.dpdk.org/guides/prog_guide/env_abstraction_layer.html#memory-mapping-discovery-and-memory-reservation
[3] - https://bugzilla.redhat.com/show_bug.cgi?id=1949850

Comment 2 Michael Santana 2022-03-07 15:15:52 UTC

*** This bug has been marked as a duplicate of bug 1949850 ***