Bug 1771390

Summary: [RFE] Add visibility on vhost-user tx contention
Product: Red Hat Enterprise Linux Fast Datapath Reporter: David Marchand <dmarchan>
Component: openvswitch2.12Assignee: David Marchand <dmarchan>
Status: CLOSED ERRATA QA Contact: Jean-Tsung Hsiao <jhsiao>
Severity: low Docs Contact:
Priority: unspecified    
Version: FDP 19.GCC: ctrautma, fbaudin, fleitner, gmuthukr, jhsiao, kfida, qding, ralongi, vchundur
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openvswitch2.12-2.12.0-5.el7fdn Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1740144
: 1775783 (view as bug list) Environment:
Last Closed: 2019-12-11 12:14:59 UTC Type: ---
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: 1775783    

Description David Marchand 2019-11-12 09:51:07 UTC 
+++ This bug was initially created as a clone of Bug #1740144 +++

When multiple PMD threads in OVS want to push packets through a vhost-user port, but the virtual machine did not initialise enough queues, PMD threads have to take a lock on the queues.
This can result in packets losses because of the extra cost on handling the packets.

This behavior is hard to figure out without having a deep understanding on the platform, flows and PMD configurations.

Making this visible would help to debug these kinds of issues.
Comment 2 Jean-Tsung Hsiao 2019-11-27 13:17:04 UTC 
This enhancement has been verified: https://bugzilla.redhat.com/show_bug.cgi?id=1740144#c3
Comment 4 errata-xmlrpc 2019-12-11 12:14:59 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:4206