automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: Jerin Jacob <jerinj@marvell.com>,
	daxuex.gao@intel.com, chenyux.huang@intel.com,
	lijuan.tu@intel.com, Joyce Kong <joyce.kong@arm.com>
Subject: [dpdk-test-report]|SUCCESS | dpdk-next-net-mrvl|9351bc0906| Intel-Testing
Date: 03 Jan 2023 02:48:46 -0800	[thread overview]
Message-ID: <3d8560$ji9he1@fmsmga007-auth.fm.intel.com> (raw)

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


Test-Label: intel-Testing
Test-Status: SUCCESS 
_Testing PASS 

DPDK git repo: dpdk-next-net-mrvl

commit 9351bc0906b4585fd9d50a89f9f6d2f091d3e822
Author: Joyce Kong <joyce.kong@arm.com>
Date:   Thu Sep 15 14:58:25 2022 +0800

    net/memif: add a Tx fast path
    
    For memif non-zero-copy mode, there is a branch to compare
    the mbuf and memif buffer size during memory copying. If all
    mbufs come from the same mempool, and memif buf size >= mbuf
    size, add a fast Tx memory copy path without the comparing
    branch and with mbuf bulk free, otherwise still run the
    original Tx path.
    The removal of the branch and bulk free lead to considerable
    performance uplift.
    
    Test with 1p1q on Ampere Altra AArch64 server,
    --------------------------------------------
      buf size  | memif >= mbuf | memif < mbuf |
    --------------------------------------------
    non-zc gain |    10.82%     |     0.04%    |
    --------------------------------------------
       zc gain  |     8.86%     |     3.18%    |
    --------------------------------------------
    
    Test with 1p1q on Cascade Lake Xeon X86server,
    --------------------------------------------
      buf size  | memif >= mbuf | memif < mbuf |
    --------------------------------------------
    non-zc gain |     7.32%     |    -0.85%    |
    --------------------------------------------
       zc gain  |    12.75%     |    -0.16%    |
    --------------------------------------------
    
    Signed-off-by: Joyce Kong <joyce.kong@arm.com>
    Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
    Acked-by: Morten Brørup <mb@smartsharesystems.com>

Testing Summary : 18 Case Done, 18 Successful, 0 Failures

Testbed #1: 9 Case Done, 9 Successful, 0 Failures 
	* Test result details:
	  +-------------+---------------------------+-------+
	  | suite       | case                      | status|
	  +-------------+---------------------------+-------+
	  | asan_smoke  | test_rxtx_with_ASan_enable| passed|
	  | pf_smoke    | test_pf_jumbo_frames      | passed|
	  | pf_smoke    | test_pf_rss               | passed|
	  | pf_smoke    | test_pf_tx_rx_queue       | passed|
	  | vf_smoke    | test_vf_jumbo_frames      | passed|
	  | vf_smoke    | test_vf_rss               | passed|
	  | vf_smoke    | test_vf_tx_rx_queue       | passed|
	  | virtio_smoke| test_virtio_loopback      | passed|
	  | virtio_smoke| test_virtio_pvp           | passed|
	  +-------------+---------------------------+-------+
	* Environment:
	  OS : Ubuntu 20.04.5 LTS       
	  Kernel : 5.8.0-63-generic         
	  GCC : 9.4.0-1ubuntu1~20.04.1        
	  NIC : Ethernet Controller E810-C for SFP         
	  Target : x86_64-native-linuxapp-gcc      

Testbed #2: 9 Case Done, 9 Successful, 0 Failures 
	* Test result details:
	  +-------------+---------------------------+-------+
	  | suite       | case                      | status|
	  +-------------+---------------------------+-------+
	  | asan_smoke  | test_rxtx_with_ASan_enable| passed|
	  | pf_smoke    | test_pf_jumbo_frames      | passed|
	  | pf_smoke    | test_pf_rss               | passed|
	  | pf_smoke    | test_pf_tx_rx_queue       | passed|
	  | vf_smoke    | test_vf_rss               | passed|
	  | vf_smoke    | test_vf_tx_rx_queue       | passed|
	  | vf_smoke    | test_vf_jumbo_frames      | n/a   |
	  | virtio_smoke| test_virtio_loopback      | passed|
	  | virtio_smoke| test_virtio_pvp           | passed|
	  +-------------+---------------------------+-------+
	* Environment:
	  OS : Ubuntu 20.04.5 LTS       
	  Kernel : 5.13.0-30-generic         
	  GCC : 9.4.0-1ubuntu1~20.04.1        
	  NIC : Ethernet Controller XL710 for 40GbE QSFP+         
	  Target : x86_64-native-linuxapp-gcc      

TestPlan:
	   pf_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/pf_smoke_test_plan.rst
	   vf_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/vf_smoke_test_plan.rst
	   asan_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/asan_smoke_test_plan.rst

TestSuite:
	   pf_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_pf_smoke.py
	   vf_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_vf_smoke.py
	   virtio_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_virtio_smoke.py
	   asan_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_asan_smoke.py


DPDK STV team

                 reply	other threads:[~2023-01-03 10:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='3d8560$ji9he1@fmsmga007-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=chenyux.huang@intel.com \
    --cc=daxuex.gao@intel.com \
    --cc=jerinj@marvell.com \
    --cc=joyce.kong@arm.com \
    --cc=lijuan.tu@intel.com \
    --cc=test-report@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).