On 11/10/2019 22:19, Kevin Traynor wrote:
> On 11/10/2019 17:33, Ju-Hyoung Lee wrote:
>> Is there any other partners have done DPDK performance test with different 
>> OS distro?
> 
> There was a few other perf testings reported elsewhere in reply to this
> thread and there wasn't other perf drop reported. I only know the distro
> of the Red Hat testing (RHEL). To summarize,
> 
> Intel and IBM reported perf testing, Red Hat did perf testing with
> SR-IOV. There was also some OVS perf testing from Ian, but that may be a
> little less relevant as there is a lot of OVS involved in the datapath.
> 
> Mellanox haven't reported their testing results yet, so seen as you are
> using a Mellanox NIC their results may be interesting.
> 
> I've ran some OVS and testpmd tests on RHEL. For testpmd I see perf
> within 0.06% of 18.11.2.
> 
>> I wonder if this is distro-specific or Azure-specific.
>>
> 
> These are the netvsc/failsafe changes, in case you wanted to clone the
> repo (git://dpdk.org/dpdk-stable branch 18.11) and revert them for
> investigating:
> $ git log --oneline  v18.11.2..v18.11.3-rc2 | grep -e netvsc -e failsafe
> 822c98c8a net/netvsc: fix definition of offload values
> a8a965216 net/netvsc: fix xstats for VF device
> 9fd8123bd net/netvsc: fix xstats id
> ddc352a3f net/netvsc: fix RSS offload settings
> ad4093aac net/netvsc: initialize VF spinlock
> 2f05eb233 net/failsafe: fix reported device info
> 

Hi Abishek/Ju,

Any update on this issue? Were you able to bisect to which commit is
causing an issue in your tests?

thanks,
Kevin.

>> Ju
>>
>> -----Original Message-----
>> From: Abhishek Marathe <abhishek.mara...@microsoft.com> 
>> Sent: Friday, October 11, 2019 9:30 AM
>> To: Kevin Traynor <ktray...@redhat.com>; sta...@dpdk.org
>> Cc: dev@dpdk.org; Akhil Goyal <akhil.go...@nxp.com>; Ali Alnubani 
>> <alia...@mellanox.com>; benjamin.wal...@intel.com; David Christensen 
>> <d...@linux.vnet.ibm.com>; Hemant Agrawal <hemant.agra...@nxp.com>; Ian 
>> Stokes <ian.sto...@intel.com>; Jerin Jacob <jer...@marvell.com>; John 
>> McNamara <john.mcnam...@intel.com>; Ju-Hyoung Lee <juh...@microsoft.com>; 
>> Luca Boccassi <bl...@debian.org>; Pei Zhang <pezh...@redhat.com>; 
>> pingx...@intel.com; qian.q...@intel.com; Raslan Darawsheh 
>> <rasl...@mellanox.com>; Thomas Monjalon <tho...@monjalon.net>; 
>> yuan.p...@intel.com; zhaoyan.c...@intel.com
>> Subject: RE: 18.11.3 (LTS) patches review and test
>>
>> Hi All,
>>
>> Our Findings while testing DPDK 18.11.3-rc2 release:
>> 1. PERF-DPDK-MULTICORE-PPS-F32: This testcase is failing for almost all the 
>> distros. I can reproduce the problem but there are no errors in the Kernel 
>> logs / Test Execution logs. It seems that failure is due to lower 
>> performance than threshold. As this testcase was not failing for the 
>> previous releases, we are going to investigate it further.
> 
> What is Standard_F32s_v2? What is the result and the threshold?
> 
> thanks,
> Kevin.
> 
>> 2. We are getting low performance for Ubuntu distribution failed testcases.
>>
>> Test Result:
>>
>> DPDK v18.11.3-rc2 was validated on Azure for Canonical UbuntuServer 
>> 16.04-LTS latest, Canonical UbuntuServer 18.04-DAILY-LTS latest, RedHat RHEL 
>> 7-RAW latest, RedHat RHEL 7.5 latest, Openlogic CentOS 7.5 latest, SUSE SLES 
>> 15 latest.
>> Tested with Mellanox and netvsc poll-mode drivers.
>> The tests were executed using LISAv2 framework 
>> (https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FLIS%2FLISAv2&amp;data=02%7C01%7Cjuhlee%40microsoft.com%7C8ad50d4d779c486a550e08d74e68350b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637064081778210151&amp;sdata=vcX1Tnc4v8w2RbdL4xNOQbkrvba4R5lyymiznEYj4Dk%3D&amp;reserved=0).
>>
>> Test case description:
>>
>> * VERIFY-DPDK-COMPLIANCE - verifies kernel is supported and that the build 
>> is successful
>> * VERIFY-DPDK-BUILD-AND-TESTPMD-TEST - verifies using testpmd that packets 
>> can be sent from a VM to another VM
>> * VERIFY-SRIOV-FAILSAFE-FOR-DPDK - disables/enables Accelerated Networking 
>> for the NICs under test and makes sure DPDK works in both scenarios
>> * VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC - disables/enables Accelerated 
>> Networking for the NICs while generating traffic using testpmd
>>
>> * PERF-DPDK-FWD-PPS-DS15 - verifies DPDK forwarding performance using 
>> testpmd on 2, 4, 8 cores, rx and io mode on size Standard_DS15_v2
>> * PERF-DPDK-SINGLE-CORE-PPS-DS4 - verifies DPDK performance using testpmd on 
>> 1 core, rx and io mode on size Standard_DS4_v2
>> * PERF-DPDK-SINGLE-CORE-PPS-DS15 - verifies DPDK performance using testpmd 
>> on 1 core, rx and io mode on size Standard_DS15_v2
>> * PERF-DPDK-MULTICORE-PPS-DS15 - verifies DPDK performance using testpmd on 
>> 2, 4, 8 cores, rx and io mode on size Standard_DS15_v2
>> * PERF-DPDK-MULTICORE-PPS-F32 - verifies DPDK performance using testpmd on 
>> 2, 4, 8, 16 cores, rx and io mode on size Standard_F32s_v2
>>
>> * DPDK-RING-LATENCY - verifies DPDK CPU latency using 
>> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fshemminger%2Fdpdk-ring-ping.git&amp;data=02%7C01%7Cjuhlee%40microsoft.com%7C8ad50d4d779c486a550e08d74e68350b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637064081778210151&amp;sdata=w1ShwRLxHcqibCZKwDmyxWjH5AIlz096gLsek4J1zGY%3D&amp;reserved=0
>> * VERIFY-DPDK-PRIMARY-SECONDARY-PROCESSES - verifies primary / secondary 
>> processes support for DPDK. Runs only on RHEL and Ubuntu distros with Linux 
>> kernel >= 4.20
>>
>> * VERIFY-DPDK-OVS - builds OVS with DPDK support and tests if the OVS DPDK 
>> ports can be created. Runs only on Ubuntu distro.
>> * VERIFY-DPDK-VPP - builds VPP with DPDK support and tests if the VPP ports 
>> are present. Runs only on RHEL and Ubuntu distros.
>> * VERIFY-DPDK-NFF-GO - builds NFF-GO with DPDK support and runs the 
>> functional tests from the NFF-GO repository. Runs only on Ubuntu distro.
>>
>>  DPDK job exited with status: UNSTABLE - 
>> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinuxpipeline.westus2.cloudapp.azure.com%2Fjob%2FDPDK%2Fjob%2Fpipeline-dpdk-validation%2Fjob%2Fmaster%2F252%2F&amp;data=02%7C01%7Cjuhlee%40microsoft.com%7C8ad50d4d779c486a550e08d74e68350b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637064081778210151&amp;sdata=jy8T4kTBur4KpeCWFix4s5Pr8KiYFnSW9RPS9Cbjz4I%3D&amp;reserved=0.
>>  
>>
>> Test results for DPDK 'v18.11.3-rc2' and Azure image: 'Canonical 
>> UbuntuServer 16.04-LTS latest': 
>>  
>> * PERF-DPDK-SINGLE-CORE-PPS-DS4: FAILED 
>> * VERIFY-DPDK-OVS: PASSED 
>> * VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED 
>> * VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED 
>> * PERF-DPDK-MULTICORE-PPS-F32: FAILED 
>> * VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: ABORTED 
>> * PERF-DPDK-FWD-PPS-DS15: FAILED 
>> * PERF-DPDK-SINGLE-CORE-PPS-DS15: FAILED 
>> * PERF-DPDK-MULTICORE-PPS-DS15: FAILED 
>> * VERIFY-DPDK-COMPLIANCE: PASSED 
>> * VERIFY-DPDK-RING-LATENCY: PASSED 
>>
>> Test results for DPDK 'v18.11.3-rc2' and Azure image: 'Canonical 
>> UbuntuServer 18.04-DAILY-LTS latest': 
>>  
>> * PERF-DPDK-SINGLE-CORE-PPS-DS4: FAILED 
>> * VERIFY-DPDK-OVS: PASSED 
>> * VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED 
>> * VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED 
>> * PERF-DPDK-MULTICORE-PPS-F32: FAILED 
>> * VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED 
>> * PERF-DPDK-FWD-PPS-DS15: FAILED 
>> * PERF-DPDK-SINGLE-CORE-PPS-DS15: FAILED 
>> * PERF-DPDK-MULTICORE-PPS-DS15: ABORTED 
>> * VERIFY-DPDK-COMPLIANCE: PASSED 
>> * VERIFY-DPDK-RING-LATENCY: PASSED 
>>
>> Test results for DPDK 'v18.11.3-rc2' and Azure image: 'RedHat RHEL 7-RAW 
>> latest': 
>>  
>> * PERF-DPDK-SINGLE-CORE-PPS-DS4: FAILED 
>> * VERIFY-DPDK-OVS: SKIPPED 
>> * VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED 
>> * VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED 
>> * PERF-DPDK-MULTICORE-PPS-F32: ABORTED 
>> * VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED 
>> * PERF-DPDK-FWD-PPS-DS15: PASSED 
>> * PERF-DPDK-SINGLE-CORE-PPS-DS15: PASSED 
>> * PERF-DPDK-MULTICORE-PPS-DS15: PASSED 
>> * VERIFY-DPDK-COMPLIANCE: PASSED 
>> * VERIFY-DPDK-RING-LATENCY: PASSED 
>>
>> Test results for DPDK 'v18.11.3-rc2' and Azure image: 'RedHat RHEL 7.5 
>> latest': 
>>  
>> * PERF-DPDK-SINGLE-CORE-PPS-DS4: PASSED 
>> * VERIFY-DPDK-OVS: SKIPPED 
>> * VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED 
>> * VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED 
>> * PERF-DPDK-MULTICORE-PPS-F32: ABORTED 
>> * VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED 
>> * PERF-DPDK-FWD-PPS-DS15: PASSED 
>> * PERF-DPDK-SINGLE-CORE-PPS-DS15: PASSED 
>> * PERF-DPDK-MULTICORE-PPS-DS15: PASSED 
>> * VERIFY-DPDK-COMPLIANCE: PASSED 
>> * VERIFY-DPDK-RING-LATENCY: PASSED 
>>
>> Test results for DPDK 'v18.11.3-rc2' and Azure image: 'Openlogic CentOS 7.5 
>> latest': 
>>  
>> * PERF-DPDK-SINGLE-CORE-PPS-DS4: PASSED 
>> * VERIFY-DPDK-OVS: SKIPPED 
>> * VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED 
>> * VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED 
>> * PERF-DPDK-MULTICORE-PPS-F32: PASSED 
>> * VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED 
>> * PERF-DPDK-FWD-PPS-DS15: PASSED 
>> * PERF-DPDK-SINGLE-CORE-PPS-DS15: PASSED 
>> * PERF-DPDK-MULTICORE-PPS-DS15: PASSED 
>> * VERIFY-DPDK-COMPLIANCE: PASSED 
>> * VERIFY-DPDK-RING-LATENCY: PASSED 
>>
>> Test results for DPDK 'v18.11.3-rc2' and Azure image: 'SUSE SLES 15 latest': 
>>  
>> * PERF-DPDK-SINGLE-CORE-PPS-DS4: PASSED 
>> * VERIFY-DPDK-OVS: SKIPPED 
>> * VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED 
>> * VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED 
>> * PERF-DPDK-MULTICORE-PPS-F32: FAILED 
>> * VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED 
>> * PERF-DPDK-FWD-PPS-DS15: PASSED 
>> * PERF-DPDK-SINGLE-CORE-PPS-DS15: PASSED 
>> * PERF-DPDK-MULTICORE-PPS-DS15: PASSED 
>> * VERIFY-DPDK-COMPLIANCE: PASSED 
>> * VERIFY-DPDK-RING-LATENCY: PASSED 
>>
>> Regards,
>> Abhishek
>>
>> -----Original Message-----
>> From: Kevin Traynor <ktray...@redhat.com> 
>> Sent: Thursday, October 3, 2019 6:21 AM
>> To: sta...@dpdk.org
>> Cc: dev@dpdk.org; Abhishek Marathe <abhishek.mara...@microsoft.com>; Akhil 
>> Goyal <akhil.go...@nxp.com>; Ali Alnubani <alia...@mellanox.com>; 
>> benjamin.wal...@intel.com; David Christensen <d...@linux.vnet.ibm.com>; 
>> Hemant Agrawal <hemant.agra...@nxp.com>; Ian Stokes <ian.sto...@intel.com>; 
>> Jerin Jacob <jer...@marvell.com>; John McNamara <john.mcnam...@intel.com>; 
>> Ju-Hyoung Lee <juh...@microsoft.com>; Kevin Traynor <ktray...@redhat.com>; 
>> Luca Boccassi <bl...@debian.org>; Pei Zhang <pezh...@redhat.com>; 
>> pingx...@intel.com; qian.q...@intel.com; Raslan Darawsheh 
>> <rasl...@mellanox.com>; Thomas Monjalon <tho...@monjalon.net>; 
>> yuan.p...@intel.com; zhaoyan.c...@intel.com
>> Subject: 18.11.3 (LTS) patches review and test
>>
>> Hi all,
>>
>> Here is a list of patches targeted for LTS release 18.11.3. 
>>
>> The planned date for the final release is 14th October.
>>
>> Please note the commits since RC1 below. They are primarily to address some 
>> build issues for 32-bit with meson and FreeBSD.
>> As such, I would expect that most RC1 testing is still valid and does not 
>> need to be repeated.
>>
>> Please help with testing and validation of your use cases and report any 
>> issues/results in reply 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdpdk.org%2Fbrowse%2Fdpdk-stable%2Ftag%2F%3Fid%3Dv18.11.3-rc2&amp;data=02%7C01%7Cjuhlee%40microsoft.com%7C8ad50d4d779c486a550e08d74e68350b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637064081778210151&amp;sdata=ZFrDBkGh1jgKt7h8jEqv7BtZ%2FhGvPH7xGw%2B6vvGHk4o%3D&amp;reserved=0
>>
>> These patches are located at branch 18.11 of dpdk-stable repo:
>>     
>> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdpdk.org%2Fbrowse%2Fdpdk-stable%2F&amp;data=02%7C01%7Cjuhlee%40microsoft.com%7C8ad50d4d779c486a550e08d74e68350b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637064081778210151&amp;sdata=BqMqA%2FKc%2BOg%2FNrXO%2Bf1k0Vqw5xjONqqYVPPh4js2H9M%3D&amp;reserved=0
>>
>> Commits since RC1:
>> 9e7c637c6 build: add libatomic dependency for 32-bit clang 6c576d41c mem: 
>> mark unused function in 32-bit builds
>> 7ffe32a15 build: remove unnecessary large file support defines 5c3c20a8a 
>> build: enable large file support on 32-bit
>> 5633216d4 net/nfp: disable for 32-bit meson builds
>> c97d4cd35 build: set RTE_ARCH_64 based on pointer size
>> 86e56d5f9 ethdev: fix endian annotation for SPI item d908ee9de build: enable 
>> BSD features visibility for FreeBSD
>>
>> Thanks.
>>
>> Kevin Traynor
>>
>> ---

[snipped list of patches]

Reply via email to