patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Ian Stokes <ian.stokes@intel.com>, dpdk stable <stable@dpdk.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] 18.11.1 patches review and test
Date: Wed, 3 Apr 2019 15:29:09 +0100	[thread overview]
Message-ID: <d9555e8e-5353-9a4f-856f-d74e24defb1f@redhat.com> (raw)
In-Reply-To: <d6950a84-cc4a-0833-cc33-ce363c21fc83@intel.com>

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
> 


      reply	other threads:[~2019-04-03 14:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 15:10 [dpdk-stable] " Kevin Traynor
2019-03-27 14:41 ` [dpdk-stable] [dpdk-dev] " Ali Alnubani
2019-03-27 16:43   ` Kevin Traynor
2019-04-03  9:16 ` Ian Stokes
2019-04-03 14:29   ` 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=d9555e8e-5353-9a4f-856f-d74e24defb1f@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ian.stokes@intel.com \
    --cc=stable@dpdk.org \
    /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).