DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@mellanox.com>
To: Ian Stokes <ian.stokes@intel.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	dpdk stable <stable@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Sitong Liu <siliu@redhat.com>,
	Pei Zhang <pezhang@redhat.com>,
	Raslan Darawsheh <rasland@mellanox.com>,
	"qian.q.xu@intel.com" <qian.q.xu@intel.com>,
	Ju-Hyoung Lee <juhlee@microsoft.com>,
	David Christensen <drc@linux.vnet.ibm.com>,
	"benjamin.walker@intel.com" <benjamin.walker@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	John McNamara <john.mcnamara@intel.com>,
	Luca Boccassi <bluca@debian.org>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	Akhil Goyal <akhil.goyal@nxp.com>
Subject: Re: [dpdk-dev] 18.11.2 (LTS) patches review and test
Date: Thu, 30 May 2019 11:59:34 +0000	[thread overview]
Message-ID: <DB6PR0501MB2167B1DFB7C580F4D113EC5BD7180@DB6PR0501MB2167.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <690a2f09-33f4-2c90-36ff-628f02630d2f@intel.com>

> -----Original Message-----
> From: Ian Stokes <ian.stokes@intel.com>
> Sent: Thursday, May 30, 2019 11:16 AM
> To: Kevin Traynor <ktraynor@redhat.com>; dpdk stable <stable@dpdk.org>
> Cc: dev@dpdk.org; Sitong Liu <siliu@redhat.com>; Pei Zhang
> <pezhang@redhat.com>; Raslan Darawsheh <rasland@mellanox.com>;
> qian.q.xu@intel.com; Ju-Hyoung Lee <juhlee@microsoft.com>; Ali Alnubani
> <alialnu@mellanox.com>; David Christensen <drc@linux.vnet.ibm.com>;
> benjamin.walker@intel.com; Thomas Monjalon <thomas@monjalon.net>;
> John McNamara <john.mcnamara@intel.com>; Luca Boccassi
> <bluca@debian.org>; Jerin Jacob Kollanukkaran <jerinj@marvell.com>;
> Hemant Agrawal <hemant.agrawal@nxp.com>; Akhil Goyal
> <akhil.goyal@nxp.com>
> Subject: Re: 18.11.2 (LTS) patches review and test
> 
> On 5/21/2019 3:01 PM, Kevin Traynor wrote:
> > Hi all,
> >
> > Here is a list of patches targeted for LTS release 18.11.2.
> >
> > The planned date for the final release is 11th June.
> >
> > Please help with testing and validation of your use cases and report
> > any issues/results. For the final release I will update the release
> > notes with fixes and reported validations.

<removed>

> >
> > Thanks.
> >
> > Kevin Traynor
> >
> 
> Hi Kevin,
> 
> I've validated with current head OVS Master and OVS 2.11.1 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_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.
> * 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
> 
> Regards
> Ian

Hi,

I validated this version and sent our testing matrix:
http://mails.dpdk.org/archives/stable/2019-May/015198.html

Thanks,
Ali

  reply	other threads:[~2019-05-30 11:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-21 14:01 Kevin Traynor
2019-05-24 16:46 ` [dpdk-dev] [dpdk-stable] " dwilder
2019-05-24 16:51   ` Kevin Traynor
2019-05-30 22:32     ` Ju-Hyoung Lee
2019-05-30  8:15 ` [dpdk-dev] " Ian Stokes
2019-05-30 11:59   ` Ali Alnubani [this message]
2019-06-04  8:11 ` Pei Zhang

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=DB6PR0501MB2167B1DFB7C580F4D113EC5BD7180@DB6PR0501MB2167.eurprd05.prod.outlook.com \
    --to=alialnu@mellanox.com \
    --cc=akhil.goyal@nxp.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=ktraynor@redhat.com \
    --cc=pezhang@redhat.com \
    --cc=qian.q.xu@intel.com \
    --cc=rasland@mellanox.com \
    --cc=siliu@redhat.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).