automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: daxuex.gao@intel.com, chenyux.huang@intel.com,
	lijuan.tu@intel.com, Gregory Etelson <getelson@nvidia.com>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Ferruh Yigit <ferruh.yigit@amd.com>
Subject: [dpdk-test-report]|SUCCESS | dpdk-next-net|4fb01feb43| Intel-Testing
Date: 19 Jan 2023 07:16:32 -0800	[thread overview]
Message-ID: <8251fc$kkc2p8@orsmga001-auth.jf.intel.com> (raw)

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


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

DPDK git repo: dpdk-next-net

commit 4fb01feb4332431241e39fbd7716cd233109e46c
Author: Gregory Etelson <getelson@nvidia.com>
Date:   Thu Jan 19 15:25:06 2023 +0200

    ethdev: add quota flow action and item
    
    Quota action limits traffic according to pre-defined configuration.
    Quota reflects overall traffic usage regardless bandwidth.
    Quota flow action initialized with signed tokens number value.
    Quota flow action updates tokens number according to
    these rules:
    1. if quota was configured to count packet length, for each packet
       of size S, tokens number reduced by S.
    2. If quota was configured to count packets, each packet decrements
       tokens number.
    quota action sets packet metadata according to a number of remaining
    tokens number:
      PASS - remaining tokens number is non-negative.
      BLOCK - remaining tokens number is negative.
    
    Quota flow item matches on that data
    
    Application updates tokens number in quota flow action
    with SET or ADD calls:
     SET(QUOTA, val) - arm quota with new tokens number set to val
     ADD(QUOTA, val) - increase existing quota tokens number by val
    
    Both SET and ADD return to application number of tokens stored in port
    before update.
    
    If quota state was BLOCK (negative action tokens number)
    application can change it to PASS after providing enough tokens to
    raise action tokens number to 0 or above.
    
    Application must create a rule with quota action to mark flow and
    match on the mark with quota item in following flow rule.
    
    Signed-off-by: Gregory Etelson <getelson@nvidia.com>
    Acked-by: Ori Kam <orika@nvidia.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-19 15:26 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='8251fc$kkc2p8@orsmga001-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=chenyux.huang@intel.com \
    --cc=daxuex.gao@intel.com \
    --cc=ferruh.yigit@amd.com \
    --cc=getelson@nvidia.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).