Description of problem:

Clone of BZ 1628669 for RHOSP13.

(a) what OSP-10 change is the root cause of the regression:     
Prior to OVS 2.9 automatic assignment of Rxqs to PMDs
    (i.e. CPUs) was done by assigning Rxqs in an ascending
    port/queue order, round robined across the available
    PMDs.
    
    That was changed in OVS 2.9 to order the Rxqs by the
    measured processing cycles for each, in order to try
    and keep the busiest Rxqs on different PMDs.
    
    For the most part the new scheme should be better, but
    there could be situations where a user prefers a
    port/queue scheme because Rxqs from a single port are
    more likely to be spread across multiple cores, and/or
    traffic is very bursty/unpredictable.
    
    Add the option to have a port/queue based assignment.

(b) when was that change introduced: In OVS2.9 
(c) the impact of that regression on customers: Possible performance degradation from OVS2.6 to OVS2.9 

Primary OVS BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1616001
RHOSP10 OVS BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1628669

Version-Release number of selected component (if applicable):
Red Hat OpenStack 13

Expected results:
This BZ has created to sync the OVS patch to RHOSP13 once it validated from Bz:1628669