After some discussion upstream with OVS contributors there is alot of other code (specifically in the DPDK codebase) which is materially impacted with the fallback approach.
The consensus was that it would be better to simply disable mlock when executing in a container - new PR raised to this effect: https://github.com/openvswitch/ovs/pull/358 ** Changed in: openvswitch (Ubuntu) Status: Triaged => In Progress ** Summary changed: - locked memory allocation failure should fallback to unlocked memory + mlock should be disabled when running in containers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920892 Title: mlock should be disabled when running in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1920892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
