OVS with DPDK aims to be device agnostic i.e. regardless of the driver, ports should be initialized, configured and used largely in the same manner. APIs such as the eth dev API help achieve this to a degree but specific device capabilities and driver behavior beneath the eth dev API make a truly generic approach in OVS DPDK difficult. This talk will present a number of examples of this encountered to date, how they were resolved within OVS DPDK but how they could be better resolved within the DPDK code base.
