From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 1E657A0679 for ; Wed, 3 Apr 2019 16:29:18 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 501E51B2AC; Wed, 3 Apr 2019 16:29:17 +0200 (CEST) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 0C6F91B14C; Wed, 3 Apr 2019 16:29:13 +0200 (CEST) Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 6B58D2D7E4; Wed, 3 Apr 2019 14:29:12 +0000 (UTC) Received: from [10.40.205.77] (unknown [10.40.205.77]) by smtp.corp.redhat.com (Postfix) with ESMTP id D330860144; Wed, 3 Apr 2019 14:29:10 +0000 (UTC) To: Ian Stokes , dpdk stable Cc: dev@dpdk.org References: <20190322151023.6616-1-ktraynor@redhat.com> From: Kevin Traynor Message-ID: Date: Wed, 3 Apr 2019 15:29:09 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Wed, 03 Apr 2019 14:29:12 +0000 (UTC) Subject: Re: [dpdk-stable] [dpdk-dev] 18.11.1 patches review and test X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" 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 >