[dpdk-stable] [dpdk-dev] 18.11.1 patches review and test

[Kevin Traynor]

On 03/04/2019 10:16, Ian Stokes wrote:
> On 3/22/2019 3:10 PM, Kevin Traynor wrote:
>> Hi all,
>>
>> Here is a list of patches targeted for LTS release 18.11.1. Please
>> help review and test. The planned date for the final release is
>> April 8th. Before that, please shout if anyone has objections with these
>> patches being applied.
>>
>> Also for the companies committed to running regression tests,
>> please run the tests and report any issue before the release date.
>>
>> To avoid further delays, in the absence of any reported release blockers
>> the release will go ahead on April 8th. I will add some release notes
>> regarding list of bugfixes and areas validated.
> 
> Hi Kevin,
> 
> I've validated with current head OVS Master and OVS 2.11.0 with VSPERF. 
> Tested with i40e (X710), ixgbe (82599ES) and igb(I350) devices.
> 
> Following tests were conducted and passed:
> 

Great - thanks for this Ian. I will add this (or summary) into the
release notes.

Kevin.

> * vswitch_p2p_tput: vSwitch - configure switch and execute RFC2544 
> throughput test.
> * vswitch_p2p_cont: vSwitch - configure switch and execute RFC2544 
> continuous stream test.
> * vswitch_pvp_tput: vSwitch - configure switch, vnf and execute RFC2544 
> throughput test.
> * vswitch_pvp_cont: vSwitch - configure switch, vnf and execute RFC2544 
> continuous stream test.
> * ovsdpdk_hotplug_attach: Ensure successful port-add after binding a 
> device to igb_uio after ovs-vswitchd is launched.
> * ovsdpdk_mq_p2p_rxqs: Setup rxqs on NIC port.
> * ovsdpdk_mq_pvp_rxqs: Setup rxqs on vhost user port.
> * ovsdpdk_mq_pvp_rxqs_linux_bridge: Confirm traffic received over vhost 
> RXQs with Linux virtio device in guest.
> * ovsdpdk_mq_pvp_rxqs_testpmd: Confirm traffic received over vhost RXQs 
> with DPDK device in guest.
> * ovsdpdk_vhostuser_client: Test vhost-user client mode. 
>                * ovsdpdk_vhostuser_client_reconnect: Test vhost-user 
> client mode reconnect feature.
> * ovsdpdk_vhostuser_server: Test vhost-user server mode. 
> 
> * ovsdpdk_vhostuser_sock_dir: Verify functionality of vhost-sock-dir flag.
> * ovsdpdk_vdev_add_null_pmd: Test addition of port using the null DPDK 
> PMD driver.
> * ovsdpdk_vdev_del_null_pmd: Test deletion of port using the null DPDK 
> PMD driver.
> * ovsdpdk_vdev_add_af_packet_pmd: Test addition of port using the 
> af_packet DPDK PMD driver.
> * ovsdpdk_vdev_del_af_packet_pmd: Test deletion of port using the 
> af_packet DPDK PMD driver.
> * ovsdpdk_numa: Test vhost-user NUMA support. Vhostuser PMD threads 
> should migrate to the same numa slot, where QEMU is executed.
> * ovsdpdk_jumbo_p2p: Ensure that jumbo frames are received, processed 
> and forwarded correctly by DPDK physical ports.
> * ovsdpdk_jumbo_pvp: Ensure that jumbo frames are received, processed 
> and forwarded correctly by DPDK vhost-user ports.
> * ovsdpdk_jumbo_p2p_upper_bound: Ensure that jumbo frames above the 
> configured Rx port's MTU are not accepted.
> * ovsdpdk_jumbo_mtu_upper_bound_vport: Verify that the upper bound limit 
> is enforced for OvS DPDK vhost-user ports.
> * ovsdpdk_rate_p2p: Ensure when a user creates a rate limiting physical 
> interface that the traffic is limited to the specified policer rate in a 
> p2p setup.
> * ovsdpdk_rate_pvp: Ensure when a user creates a rate limiting vHost 
> User interface that the traffic is limited to the specified policer rate 
> in a pvp setup.
> * ovsdpdk_qos_p2p: In a p2p setup, ensure when a QoS egress policer is 
> created that the traffic is limited to the specified rate.
> * ovsdpdk_qos_pvp: In a pvp setup, ensure when a QoS egress policer is 
> created that the traffic is limited to the specified rate.
> 
> Regards
> Ian
>