On 11/26/2019 11:56 PM, Thomas Monjalon wrote:
A new DPDK release candidate is ready for testing:
https://git.dpdk.org/dpdk/tag/?id=v19.11-rc4
93 patches were integrated.
The release notes so far:
http://doc.dpdk.org/guides/rel_notes/release_19_11.html
It should be completed with a list of tested hardware.
This is the last release candidate for DPDK 19.11.
After -rc4 only critical bug fixes and doc updates should be accepted.
The major release should be done in a couple of days (Thanksgiving?).
Please share some release validation results
by replying to this message (at dev@dpdk.org).
Hi Thomas,
OVS validation completed by Intel on RC4 below.
* 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_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.
* phy2phy_scalability: LTD.Scalability.Flows.RFC2544.0PacketLoss
* phy2phy_scalability_cont: Phy2Phy Scalability Continuous Stream
* pvp_cont: PVP Continuous Stream
* pvvp_cont: PVVP Continuous Stream
* pvpv_cont: Two VMs in parallel with Continuous Stream
* VFIO validation
These were carried out for ixgbe (ixgbe_vf), i40e (i40e_vf) and ice pmds.
Regards
Ian
If you are preparing the next release cycle, please send your v1 patches
before the 20.02 proposal deadline, which will happen on December 6th.
It is also time to build an estimated roadmap for the next cycles.
Thank you everyone
