Bug 1860228

Summary: [RFE] OVS-DPDK TSO: Support VMs with TSO disabled/unsupported
Product: Red Hat Enterprise Linux Fast Datapath Reporter: Flavio Leitner <fleitner>
Component: openvswitch2.13Assignee: Mike Pattrick <mpattric>
Status: ASSIGNED --- QA Contact: qding
Severity: medium Docs Contact:
Priority: medium    
Version: FDP 20.ECC: cfontain, ctrautma, echaudro, hakhande, jhsiao, kzhang, qding, ralongi
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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: 1860224    
Bug Blocks: 1431717    

Description Flavio Leitner 2020-07-24 04:08:49 UTC 
Description of problem:

This bug is a request to support VMs with TSO either disabled or unsupported simultaneously with other VMs with TSO enabled.

What: The VMs supporting TSO should be able to communicate with other VMs with or without TSO support.

Why: The NFV use-cases make use of larger TCP segments, but not all VMs might support TSO.

VMs should be able to start with TSO disabled or disable TSO at runtime.

 

Acceptance criteria:

1) Run iperf3 from a virtual machine with TSO enabled connected through vhost-user in client mode to another virtual machine without TSO support also connected through vhost-user.

2) Run iperf3 from a virtual machine with TSO enabled connected through vhost-user in client mode to another physical host and see better throughput.

3) Run iperf3 from a virtual machine without TSO enabled connected through vhost-user in client mode to another physical host.