Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1701935

Summary: Provide option to disable EMC in puppet-vswitch
Product: Red Hat OpenStack Reporter: yogananth subramanian <ysubrama>
Component: puppet-vswitchAssignee: yogananth subramanian <ysubrama>
Status: CLOSED ERRATA QA Contact: nlevinki <nlevinki>
Severity: high Docs Contact:
Priority: high    
Version: 14.0 (Rocky)CC: fbaudin, jjoyce, jschluet, rheslop, skramaja, slinaber, tvignaud, vkhitrin, yrachman, ysubrama
Target Milestone: z3Keywords: Triaged, ZStream
Target Release: 14.0 (Rocky)   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: puppet-vswitch-9.3.1-0.20181013121023.6a6eac8.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-02 20:08:28 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:
Bug Depends On:    
Bug Blocks: 1701940    

Description yogananth subramanian 2019-04-22 13:44:53 UTC 
Description of problem:
Based on observation presented by Andrew Theurer[1],As the number of flows increase, the performance of OvS-DPDK with the Exact Match Cache (EMC) seems to diminish below OvS-DPDK performance with no EMC at all.
Hence an option to disable EMC.

[1] -http://www.openvswitch.org/support/ovscon2018/5/1330-theurer.pdf
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
emc-insert-inv-prob to 0


Additional info:
Comment 1 yogananth subramanian 2019-04-22 13:52:49 UTC 
*** Bug 1701934 has been marked as a duplicate of this bug. ***
Comment 17 errata-xmlrpc 2019-07-02 20:08:28 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:1672