Bug 1701937 - Provide option to disable EMC in tripleo-heat-templates
Summary: Provide option to disable EMC in tripleo-heat-templates
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 13.0 (Queens)
Hardware: All
OS: Linux
high
high
Target Milestone: z7
: 13.0 (Queens)
Assignee: yogananth subramanian
QA Contact: Sasha Smolyak
URL:
Whiteboard:
Depends On: 1701901
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-22 13:56 UTC by yogananth subramanian
Modified: 2019-07-10 13:05 UTC (History)
6 users (show)

Fixed In Version: openstack-tripleo-heat-templates-8.3.1-21.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-10 13:05:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 651201 0 'None' 'MERGED' 'Provide option to disable EMC in puppet-vswitch' 2019-11-24 14:30:29 UTC
Red Hat Product Errata RHBA-2019:1738 0 None None None 2019-07-10 13:05:23 UTC

Description yogananth subramanian 2019-04-22 13:56:04 UTC 
Description of problem:
This patch disables EMC by setting emc-insert-inv-prob to 0.

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 11 errata-xmlrpc 2019-07-10 13:05:12 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:1738
Note You need to log in before you can comment on or make changes to this bug.