DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Jiang, YuX" <yux.jiang@intel.com>
To: "Xia, Chenbo" <chenbo.xia@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	"dev (dev@dpdk.org)" <dev@dpdk.org>,
	Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: "Devlin, Michelle" <michelle.devlin@intel.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	Ferruh Yigit <ferruh.yigit@xilinx.com>
Subject: RE: release candidate 22.07-rc4
Date: Thu, 14 Jul 2022 08:17:40 +0000	[thread overview]
Message-ID: <BYAPR11MB2711E7AACF83ECA70B988DA3FE889@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <SN6PR11MB35042F76A5AE086357BD7E539C869@SN6PR11MB3504.namprd11.prod.outlook.com>

> -----Original Message-----
> From: Xia, Chenbo <chenbo.xia@intel.com>
> Sent: Tuesday, July 12, 2022 5:45 PM
> To: Jiang, YuX <yux.jiang@intel.com>; Thomas Monjalon
> <thomas@monjalon.net>; dev (dev@dpdk.org) <dev@dpdk.org>; Maxime
> Coquelin <maxime.coquelin@redhat.com>
> Cc: Devlin, Michelle <michelle.devlin@intel.com>; Mcnamara, John
> <john.mcnamara@intel.com>; Ferruh Yigit <ferruh.yigit@xilinx.com>
> Subject: RE: release candidate 22.07-rc4
> 
> > -----Original Message-----
> > From: Jiang, YuX <yux.jiang@intel.com>
> > Sent: Tuesday, July 12, 2022 5:33 PM
> > To: Thomas Monjalon <thomas@monjalon.net>; dev (dev@dpdk.org)
> > <dev@dpdk.org>
> > Cc: Devlin, Michelle <michelle.devlin@intel.com>; Mcnamara, John
> > <john.mcnamara@intel.com>; Ferruh Yigit <ferruh.yigit@xilinx.com>;
> > Xia, Chenbo <chenbo.xia@intel.com>
> > Subject: RE: release candidate 22.07-rc4
> >
> > > -----Original Message-----
> > > From: Thomas Monjalon <thomas@monjalon.net>
> > > Sent: Tuesday, July 12, 2022 6:37 AM
> > > To: announce@dpdk.org
> > > Subject: release candidate 22.07-rc4
> > >
> > > A new DPDK release candidate is ready for testing:
> > > 	https://git.dpdk.org/dpdk/tag/?id=v22.07-rc4
> > >
> > > There are 22 new patches in this snapshot.
> > >
> > > Release notes:
> > > 	https://doc.dpdk.org/guides/rel_notes/release_22_07.html
> > >
> > > This is the last release candidate.
> > > Only documentation should be updated before the release.
> > >
> > > Reviews of deprecation notices are required:
> > > https://patches.dpdk.org/bundle/dmarchand/deprecation_notices/
> > >
> > > You may share some release validation results by replying to this
> > message at
> > > dev@dpdk.org and by adding tested hardware in the release notes.
> > >
> > > Please think about sharing your roadmap now for DPDK 22.11.
> > >
> > > Thank you everyone
> > >
> > Hi
> >
> > Update the test status for Intel part. Till now dpdk22.07-rc4
> > regression is running smooth.
> > But we find one high issue about "[dpdk-
> >
> 22.07]loopback_virtio_user_server_mode/server_mode_reconnect_with_s
> pli
> > t_al
> > l_path_payload_check: the first packet payload is different from the
> > ohter packets in the same queue", Bad commit id is
> > cd79d1b030bd69df31fd401d1b48c23df0f71d00(which is used to fix the
> > performance drop of split ring)
> 
> I just found the potential root cause, Maxime helped confirm it and patch will
> be out soon.
> 
> Thanks,
> Chenbo
> 
All,

Update the test status for Intel part. Till now dpdk22.07-rc4 regression is almost finished, two new bugs are found.
The high issue about "[dpdk-22.07]loopback_virtio_user_server_mode/server_mode_reconnect_with_split_all_path_payload_check: the first packet payload is different from the ohter packets in the same queue".
	It has fix link: http://patchwork.dpdk.org/project/dpdk/patch/20220712100447.104162-1-maxime.coquelin@redhat.com/, Intel validation team has completed validtion test for the patch, no new issue is found.
Other one issue about "vswitch_sample_cbdma:perf_pvp_vhost_async_operation_with_cbdma_2_channels: virtio-user will drop all the packets when sending large 1280 Byte packets".
	It has fix link: https://patches.dpdk.org/project/dpdk/patch/20220714051106.1134222-1-wenwux.ma@intel.com/ and tested-by by Intel, but no acked-by yet.

# Basic Intel(R) NIC testing
* Build or compile:  
 *Build: cover the build test combination with latest GCC/Clang version and the popular OS revision such as Ubuntu20.04, Ubuntu22.04, Fedora36, RHEL8.6 etc.
  - All test passed.

* PF/VF(i40e, ixgbe): test scenarios including PF/VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc. 
	- All test done. No new 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 issue is found. 
	
* Intel NIC single core/NIC performance: test scenarios including PF/VF single core performance test, RFC2544 Zero packet loss performance test, etc.
	- All test done. No new issue is found.
		
# 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. Find two new bugs as above.

* Cryptodev: 
 *Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
	- All test done. No new new isue is found.
 *Performance test: test scenarios including Throughput Performance/Cryptodev Latency, etc.
	- All test done. No new new isue is found.

Best regards,
Yu Jiang

> >
> > commit cd79d1b030bd69df31fd401d1b48c23df0f71d00 (HEAD)
> > Author: Xuan Ding <xuan.ding@intel.com>
> > Date:   Thu Jul 7 06:55:13 2022 +0000
> >
> >     vhost: fix unnecessary dirty page logging
> >
> >     The dirty page logging is only required in vhost enqueue direction for
> >     live migration. This patch removes the unnecessary dirty page logging
> >     in vhost dequeue direction. Otherwise, it will result in a performance
> >     drop. Some if-else judgements are also optimized to improve
> > performance.
> >
> >     Fixes: 6d823bb302c7 ("vhost: prepare sync for descriptor to mbuf
> > refactoring")
> >     Fixes: b6eee3e83402 ("vhost: fix sync dequeue offload")
> >
> >     Signed-off-by: Xuan Ding <xuan.ding@intel.com>
> >     Reviewed-by: Jiayu Hu <jiayu.hu@intel.com>
> >     Reviewed-by: Chenbo Xia <chenbo.xia@intel.com>
> >     Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> >     Tested-by: Xingguang He <xingguang.he@intel.com>
> >
> > Best regards,
> > Yu Jiang

  reply	other threads:[~2022-07-14  8:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 22:36 Thomas Monjalon
2022-07-12  9:32 ` Jiang, YuX
2022-07-12  9:44   ` Xia, Chenbo
2022-07-14  8:17     ` Jiang, YuX [this message]
2022-07-15  7:59       ` Jiang, YuX
2022-07-15 14:18 ` Thinh Tran
2022-07-17 14:33 ` Wael Abualrub

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=BYAPR11MB2711E7AACF83ECA70B988DA3FE889@BYAPR11MB2711.namprd11.prod.outlook.com \
    --to=yux.jiang@intel.com \
    --cc=chenbo.xia@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@xilinx.com \
    --cc=john.mcnamara@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=michelle.devlin@intel.com \
    --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).