From: Kevin Traynor <ktraynor@redhat.com>
To: "Stokes, Ian" <ian.stokes@intel.com>, stable@dpdk.org
Cc: dev@dpdk.org, Akhil Goyal <akhil.goyal@nxp.com>,
Ali Alnubani <alialnu@mellanox.com>,
benjamin.walker@intel.com,
David Christensen <drc@linux.vnet.ibm.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Jerin Jacob <jerinj@marvell.com>,
John McNamara <john.mcnamara@intel.com>,
Ju-Hyoung Lee <juhlee@microsoft.com>,
Luca Boccassi <bluca@debian.org>, Pei Zhang <pezhang@redhat.com>,
pingx.yu@intel.com, qian.q.xu@intel.com,
Raslan Darawsheh <rasland@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>,
yuan.peng@intel.com, zhaoyan.chen@intel.com
Subject: Re: [dpdk-dev] 18.11.3 (LTS) patches review and test
Date: Fri, 11 Oct 2019 10:41:33 +0100 [thread overview]
Message-ID: <e0703743-da88-408b-83b6-135907b49b5c@redhat.com> (raw)
In-Reply-To: <c243e0b9-bac9-9759-c51e-e40320100cae@intel.com>
On 10/10/2019 19:39, Stokes, Ian wrote:
>
>
> On 9/13/2019 5:31 PM, Kevin Traynor wrote:
>> Hi all,
>>
>> Here is a list of patches targeted for LTS release 18.11.3.
>>
>> The planned date for the final release is 9th October.
>>
>> Please help with testing and validation of your use cases and report
>> any issues/results in reply to this mail. For the final release the
>> fixes and reported validations will be added to the release notes.
>>
>> A release candidate tarball can be found at:
>>
>> https://dpdk.org/browse/dpdk-stable/tag/?id=v18.11.3-rc1
>>
>> These patches are located at branch 18.11 of dpdk-stable repo:
>> https://dpdk.org/browse/dpdk-stable/
>>
>> Thanks.
>>
>> Kevin Traynor
>
> Hi Kevin,
>
> I've validated with current head OVS Master, 2.12.2 and OVS 2.11.3 with
> VSPERF.
> Tested with i40e (X710), i40eVF, ixgbe (82599ES), ixgbeVF, igb(I350) and
> igbVF devices.
>
> Following tests were conducted and passed:
>
> * 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
>
Thanks Ian. I might summarize it a bit to shorten and add to the release
notes.
Kevin.
> Regards
> Ian
>
>
prev parent reply other threads:[~2019-10-11 9:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 16:31 Kevin Traynor
2019-09-19 10:22 ` Yu, PingX
2019-09-19 21:33 ` Ju-Hyoung Lee
2019-09-19 22:44 ` Abhishek Marathe
2019-09-23 16:18 ` Kevin Traynor
2019-09-25 16:06 ` Kevin Traynor
2019-09-26 7:41 ` Yu, PingX
2019-10-03 13:30 ` Kevin Traynor
2019-10-08 10:22 ` Yu, PingX
2019-10-11 9:39 ` Kevin Traynor
2019-10-03 13:20 ` Kevin Traynor
[not found] ` <MWHPR21MB083248DEF72934F9291C128B9E970@MWHPR21MB0832.namprd21.prod.outlook.com>
2019-10-11 16:33 ` Ju-Hyoung Lee
2019-10-11 16:49 ` Luca Boccassi
2019-10-11 21:19 ` Kevin Traynor
2019-10-15 16:21 ` [dpdk-dev] [dpdk-stable] " Kevin Traynor
2019-10-15 17:12 ` Abhishek Marathe
2019-10-15 17:19 ` Kevin Traynor
2019-10-22 10:52 ` Kevin Traynor
2019-10-22 17:44 ` Abhishek Marathe
2019-10-22 18:02 ` Kevin Traynor
2019-10-17 13:54 ` Christian Ehrhardt
2019-10-20 13:16 ` Ali Alnubani
2019-10-21 8:54 ` Kevin Traynor
2019-10-04 2:28 ` [dpdk-dev] " Pei Zhang
2019-10-04 9:37 ` Kevin Traynor
2019-10-07 20:01 ` Thinh Tran
2019-10-07 20:11 ` Ju-Hyoung Lee
2019-10-11 9:34 ` Kevin Traynor
2019-10-10 18:39 ` Stokes, Ian
2019-10-11 9:41 ` Kevin Traynor [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e0703743-da88-408b-83b6-135907b49b5c@redhat.com \
--to=ktraynor@redhat.com \
--cc=akhil.goyal@nxp.com \
--cc=alialnu@mellanox.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=hemant.agrawal@nxp.com \
--cc=ian.stokes@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=juhlee@microsoft.com \
--cc=pezhang@redhat.com \
--cc=pingx.yu@intel.com \
--cc=qian.q.xu@intel.com \
--cc=rasland@mellanox.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yuan.peng@intel.com \
--cc=zhaoyan.chen@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).