DPDK patches and discussions
 help / color / mirror / Atom feed
From: YangHang Liu <yanghliu@redhat.com>
To: "Jiang, YuX" <yux.jiang@intel.com>
Cc: "luca.boccassi@gmail.com" <luca.boccassi@gmail.com>,
	dev <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>,
	"Peng, Yuan" <yuan.peng@intel.com>,
	 "Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
	Chao Yang <chayang@redhat.com>
Subject: Re: 20.11.7 patches review and test
Date: Fri, 9 Dec 2022 17:24:57 +0800	[thread overview]
Message-ID: <CAGYh1E_JOzmE3BU41J=3YRYqw5iykUQjKL-R15OnJLZz_fE+HQ@mail.gmail.com> (raw)
In-Reply-To: <BYAPR11MB2711FE9E4FE8FFC65E2ED832FE1A9@BYAPR11MB2711.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 5749 bytes --]

Hi  Luca,

RedHat QE does not find new issues about the 20.11.7 dpdk during the tests.

We tested below 17 scenarios and all got PASS on RHEL8:

   - 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 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

Versions:

   - kernel 4.18
   - qemu-kvm-6.2
   - DPDK
      - commit 849770ce78a1b1a4871871feafbfcd9c204ea625 (tag: v20.11.7-rc1)

Author: Luca Boccassi <bluca@debian.org>

Date:   Mon Nov 28 10:21:36 2022 +0000
version: 20.11.7-rc1
Signed-off-by: Luca Boccassi <bluca@debian.org>


NICs: X540-AT2 NIC(ixgbe, 10G)


Best Regards,
YangHang Liu


On Wed, Dec 7, 2022 at 6:23 PM Jiang, YuX <yux.jiang@intel.com> wrote:

> Hi All,
> Update the test status for Intel part. Till now dpdk20.11.7-rc1 validation
> test rate is 95%. No critical issue is found.
> 2 new bugs are found, 1 new issue is under confirming by Intel Dev.
> New bugs:
>   1, Compilation error compiling dpdk with vm_power_manager sample app  --
> Intel dev is under investigating.
>   2, vf_interrupt_pmd/nic_interrupt_VF_vfio_pci: l3fwd-power Wake up
> failed on X722 37d0
>         - Find on DPDK22.11, it has fix patch:
> https://patchwork.dpdk.org/project/dpdk/patch/20221117065726.277672-1-kaisenx.you@intel.com/
>         - Patch is not merged into main, its fix can be applied on
> LTS20.11.7-rc1 and tested passed.
>   3, inline ipsec: test failed on LTS20.11.7  -- Intel validation owner
> and dev are 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,
> Fedora36, RHEL8.4, etc.
> - All test done. One known bug: https://bugs.dpdk.org/show_bug.cgi?id=991
> net/ena build failure with gcc 12, still no fix.
> * 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 big performance drop.
> * IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test
> - QAT&SW/FIB library, etc.
> - One issue is under confirming.
>
> # 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 7.0u3, etc.
> - All test done. No new issue is found.
> * Cryptodev:
>   *Function test: test scenarios including Cryptodev API
> testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
>     - All test passed.
>   *Performance test: test scenarios including Thoughput Performance
> /Cryptodev Latency, etc.
>     - All test done.
>
> Best regards,
> Yu Jiang
>
> > -----Original Message-----
> > From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> > Sent: Monday, November 28, 2022 6:53 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>;
> > Yanghang Liu <yanghliu@redhat.com>; Peng, Yuan <yuan.peng@intel.com>;
> > Chen, Zhaoyan <zhaoyan.chen@intel.com>
> > Subject: 20.11.7 patches review and test
> >
> > Hi all,
> >
> > Here is a list of patches targeted for stable release 20.11.7.
> >
> > The planned date for the final release is the 12th of December.
> >
> > 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=v20.11.7-rc1
> >
> > These patches are located at branch 20.11 of dpdk-stable repo:
> >     https://dpdk.org/browse/dpdk-stable/
> >
> > Thanks.
> >
> > Luca Boccassi
> >
> > ---
>

[-- Attachment #2: Type: text/html, Size: 8916 bytes --]

  reply	other threads:[~2022-12-09  9:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-28 10:52 luca.boccassi
2022-11-28 11:35 ` Morten Brørup
2022-11-28 11:55   ` Luca Boccassi
2022-11-28 12:07     ` Morten Brørup
2023-04-11  7:22       ` Morten Brørup
2023-04-11  9:58         ` Luca Boccassi
2022-12-07 10:21 ` Jiang, YuX
2022-12-09  9:24   ` YangHang Liu [this message]
2022-12-09  9:50     ` Luca Boccassi
2022-12-09  9:49   ` Luca Boccassi
2022-12-12 20:01     ` Luca Boccassi
2022-12-13  9:05     ` Jiang, YuX
2022-12-13 10:12       ` Luca Boccassi
2022-12-11 16:15 ` Ali Alnubani
2022-12-12 20:00   ` Luca Boccassi

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='CAGYh1E_JOzmE3BU41J=3YRYqw5iykUQjKL-R15OnJLZz_fE+HQ@mail.gmail.com' \
    --to=yanghliu@redhat.com \
    --cc=Abhishek.Marathe@microsoft.com \
    --cc=alialnu@nvidia.com \
    --cc=benjamin.walker@intel.com \
    --cc=bluca@debian.org \
    --cc=chayang@redhat.com \
    --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=luca.boccassi@gmail.com \
    --cc=pezhang@redhat.com \
    --cc=qian.q.xu@intel.com \
    --cc=rasland@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=yuan.peng@intel.com \
    --cc=yux.jiang@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).