automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: =?utf-8?q?chenyux=2Ehuang=40intel=2Ecom=2C__David_Marchand_=3Cdavid=2Emarchand=40redhat=2Ecom=3E=2C_daxuex=2Egao=40intel=2Ecom=2C__Thomas_Monjalon_=3Cthomas=40monjalon=2Enet=3E=2C_lijuan=2Etu=40intel=2Ecom=2C__Morten_Br=C3=B8rup_=3Cmb=40smartsharesystems=2Ecom=3E?=@dpdk.org
Subject: [dpdk-test-report]|SUCCESS | dpdk|203dcc9cfe| Intel-Testing
Date: 14 Nov 2022 03:16:28 -0800	[thread overview]
Message-ID: <8483a8$sqmphi@fmsmga005-auth.fm.intel.com> (raw)

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


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

DPDK git repo: dpdk

commit 203dcc9cfe4151518bb5a5c59ee22a754e649e35
Author: Morten Brørup <mb@smartsharesystems.com>
Date:   Wed Nov 9 19:18:52 2022 +0100

    mempool: use cache for frequently updated stats
    
    When built with stats enabled (RTE_LIBRTE_MEMPOOL_STATS defined),
    the performance of mempools with caches is improved as follows.
    
    When accessing objects in the mempool, either the put_bulk and put_objs or
    the get_success_bulk and get_success_objs statistics counters are likely
    to be incremented.
    
    By adding an alternative set of these counters to the mempool cache
    structure, accessing the dedicated statistics structure is avoided
    in the likely cases where these counters are incremented.
    
    The trick here is that the cache line holding the mempool cache structure
    is accessed anyway, in order to access the 'len' or 'flushthresh' fields.
    Updating some statistics counters in the same cache line has lower
    performance cost than accessing the statistics counters in the dedicated
    statistics structure, which resides in another cache line.
    
    mempool_perf_autotest with this patch shows the following improvements in
    rate_persec.
    
    The cost of enabling mempool stats (without debug) after this patch:
    -6.8 % and -6.7 %, respectively without and with cache.
    
    Signed-off-by: Morten Brørup <mb@smartsharesystems.com>
    Reviewed-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
    Reviewed-by: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
    Acked-by: Konstantin Ananyev <konstantin.ananyev@huawei.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:[~2022-11-14 11:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 11:16 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-14  9:46 sys_stv

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='8483a8$sqmphi@fmsmga005-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc==?utf-8?q?chenyux=2Ehuang=40intel=2Ecom=2C__David_Marchand_=3Cdavid=2Emarchand=40redhat=2Ecom=3E=2C_daxuex=2Egao=40intel=2Ecom=2C__Thomas_Monjalon_=3Cthomas=40monjalon=2Enet=3E=2C_lijuan=2Etu=40intel=2Ecom=2C__Morten_Br=C3=B8rup_=3Cmb=40smartsharesystems=2Ecom=3E?=@dpdk.org \
    --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).