From: Kevin Traynor <ktraynor@redhat.com>
To: YangHang Liu <yanghliu@redhat.com>, "Xu, HailinX" <hailinx.xu@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: 21.11.4 patches review and test
Date: Wed, 19 Apr 2023 15:21:05 +0100 [thread overview]
Message-ID: <55ce3c58-8236-b99a-3fa2-313ed111afcb@redhat.com> (raw)
In-Reply-To: <CAGYh1E8V59jbftTnTa9-E_-EGR_9TPjdWuLqPah0dtcqM3VThw@mail.gmail.com>
On 19/04/2023 12:00, YangHang Liu wrote:
> Hi, Kevin
>
> RedHat QE does not find new issues about the v21.11.4-rc1 dpdk during the
> tests.
>
Hi YangHang, thanks for testing and the report.
Kevin.
> We tested below 18 scenarios and all got PASS on RHEL9:
>
> - Guest with device assignment(PF) throughput testing(1G hugepage size):
> PASS
> - Guest with device assignment(PF) throughput testing(2M hugepage size)
> : PASS
> - Guest with device assignment(VF) throughput testing: PASS
> - PVP (host dpdk testpmd as vswitch) 1Q: throughput testing: PASS
> - PVP vhost-user 2Q throughput testing: PASS
> - PVP vhost-user 1Q - cross numa node throughput testing: PASS
> - Guest with vhost-user 2 queues throughput testing: PASS
> - vhost-user reconnect with dpdk-client, qemu-server qemu reconnect: PASS
> - vhost-user reconnect with dpdk-client, qemu-server ovs reconnect: PASS
> - PVP reconnect with dpdk-client, qemu-server: PASS
> - PVP 1Q live migration testing: PASS
> - PVP 1Q cross numa node live migration testing: PASS
> - Guest with ovs+dpdk+vhost-user 1Q live migration testing: PASS
> - Guest with ovs+dpdk+vhost-user 1Q live migration testing (2M): PASS
> - Guest with ovs+dpdk+vhost-user 2Q live migration testing: PASS
> - Guest with ovs+dpdk+vhost-user 4Q live migration testing: PASS
> - Host PF + DPDK testing: PASS
> - Host VF + DPDK testing: PASS
>
> Test Versions:
>
> - qemu-kvm-6.2.0
> - kernel 5.14
> - dpdk 21.11.4-rc1
>
> git log -1
>
> commit f7dce59377b34750fdda7d1780d527233c84663f
>
> Author: Kevin Traynor <ktraynor@redhat.com>
>
> Date: Thu Apr 6 09:11:25 2023 +0100
>
> version: 21.11.4-rc1
>
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
>
>
> - Test device : X540-AT2 NIC(ixgbe, 10G)
>
> Best Regards,
> YangHang Liu
>
> On Thu, Apr 13, 2023 at 2:13 PM Xu, HailinX <hailinx.xu@intel.com> wrote:
>
>>> -----Original Message-----
>>> From: Kevin Traynor <ktraynor@redhat.com>
>>> Sent: Thursday, April 6, 2023 7:38 PM
>>> To: stable@dpdk.org
>>> Cc: dev@dpdk.org; Abhishek Marathe <Abhishek.Marathe@microsoft.com>;
>>> Ali Alnubani <alialnu@nvidia.com>; Walker, Benjamin
>>> <benjamin.walker@intel.com>; David Christensen <drc@linux.vnet.ibm.com>;
>>> Hemant Agrawal <hemant.agrawal@nxp.com>; Stokes, Ian
>>> <ian.stokes@intel.com>; Jerin Jacob <jerinj@marvell.com>; Mcnamara, John
>>> <john.mcnamara@intel.com>; Ju-Hyoung Lee <juhlee@microsoft.com>; Kevin
>>> Traynor <ktraynor@redhat.com>; Luca Boccassi <bluca@debian.org>; Pei
>>> Zhang <pezhang@redhat.com>; Xu, Qian Q <qian.q.xu@intel.com>; Raslan
>>> Darawsheh <rasland@nvidia.com>; Thomas Monjalon
>>> <thomas@monjalon.net>; yanghliu@redhat.com; Peng, Yuan
>>> <yuan.peng@intel.com>; Chen, Zhaoyan <zhaoyan.chen@intel.com>
>>> Subject: 21.11.4 patches review and test
>>>
>>> Hi all,
>>>
>>> Here is a list of patches targeted for stable release 21.11.4.
>>>
>>> The planned date for the final release is 25th April.
>>>
>>> Please help with testing and validation of your use cases and report any
>>> issues/results with reply-all 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=v21.11.4-rc1
>>>
>>> These patches are located at branch 21.11 of dpdk-stable repo:
>>> https://dpdk.org/browse/dpdk-stable/
>>>
>>> Thanks.
>>>
>>> Kevin
>>
>> HI All,
>>
>> Update the test status for Intel part. Till now dpdk21.11.4-rc1 validation
>> test rate is 85%. No critical issue is found.
>> 2 new bugs are found, 1 new issue is under confirming by Intel Dev.
>> New bugs: --20.11.8-rc1 also has these two issues
>> 1. pvp_qemu_multi_paths_port_restart:perf_pvp_qemu_vector_rx_mac:
>> performance drop about 23.5% when send small packets
>> https://bugs.dpdk.org/show_bug.cgi?id=1212 -- no fix yet
>> 2. some of the virtio tests are failing: -- Intel dev is under
>> investigating
>> # Basic Intel(R) NIC testing
>> * Build & CFLAG compile: cover the build test combination with latest
>> GCC/Clang version and the popular OS revision such as
>> Ubuntu20.04, Ubuntu22.04, Fedora35, Fedora37, RHEL8.6, RHEL8.4,
>> FreeBSD13.1, SUSE15, CentOS7.9, etc.
>> - All test done. No new dpdk issue is found.
>> * PF(i40e, ixgbe): test scenarios including
>> RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
>> - All test done. No new dpdk issue is found.
>> * VF(i40e, ixgbe): test scenarios including
>> VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
>> - All test done. No new dpdk issue is found.
>> * PF/VF(ice): test scenarios including Switch features/Package
>> Management/Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Flexible
>> Descriptor, etc.
>> - All test done. No new dpdk issue is found.
>> * Intel NIC single core/NIC performance: test scenarios including PF/VF
>> single core performance test, etc.
>> - All test done. No new dpdk issue is found.
>> * IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test
>> - QAT&SW/FIB library, etc.
>> - On going.
>>
>> # Basic cryptodev and virtio testing
>> * Virtio: both function and performance test are covered. Such as
>> PVP/Virtio_loopback/virtio-user loopback/virtio-net VM2VM perf
>> testing/VMAWARE ESXI 8.0, etc.
>> - All test done. found bug1.
>> * Cryptodev:
>> *Function test: test scenarios including Cryptodev API
>> testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
>> - Execution rate is 90%. found bug2.
>> *Performance test: test scenarios including Thoughput
>> Performance/Cryptodev Latency, etc.
>> - All test done. No new dpdk issue is found.
>>
>> Regards,
>> Xu, Hailin
>>
>>
>
next prev parent reply other threads:[~2023-04-19 14:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 11:37 Kevin Traynor
2023-04-13 6:12 ` Xu, HailinX
2023-04-19 11:00 ` YangHang Liu
2023-04-19 14:21 ` Kevin Traynor [this message]
2023-04-20 2:40 ` Xu, HailinX
2023-04-20 10:32 ` Kevin Traynor
2023-05-02 9:35 ` Kevin Traynor
2023-05-04 2:13 ` Xu, HailinX
2023-05-04 10:10 ` Kevin Traynor
2023-05-05 1:42 ` Xu, HailinX
2023-05-08 15:23 ` Kevin Traynor
2023-05-11 7:33 ` Jiang, YuX
2023-05-16 8:41 ` Kevin Traynor
2023-04-19 13:24 ` Ali Alnubani
2023-04-19 14:21 ` Kevin Traynor
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=55ce3c58-8236-b99a-3fa2-313ed111afcb@redhat.com \
--to=ktraynor@redhat.com \
--cc=hailinx.xu@intel.com \
--cc=stable@dpdk.org \
--cc=yanghliu@redhat.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).