[dpdk-test-report]|SUCCESS | dpdk-next-net|b2d3f921da| Intel-Testing

[dpdk-test-report]|SUCCESS | dpdk-next-net|b2d3f921da| Intel-Testing

[sys_stv]

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


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

DPDK git repo: dpdk-next-net

commit b2d3f921da376ceed9709389a872ac527e77b38b
Author: Gregory Etelson <getelson@nvidia.com>
Date:   Fri May 19 14:59:47 2023 +0300

    ethdev: add indirect list flow action
    
    Indirect API creates a shared flow action with unique action handle.
    Flow rules can access the shared flow action and resources related to
    that action through the indirect action handle.
    In addition, the API allows to update existing shared flow action
    configuration.  After the update completes, new action configuration
    is available to all flows that reference that shared action.
    
    Indirect actions list expands the indirect action API:
    • Indirect action list creates a handle for one or several
      flow actions, while legacy indirect action handle references
      single action only.
      Input flow actions arranged in END terminated list.
    • Flow rule can provide rule specific configuration parameters to
      existing shared handle.
      Updates of flow rule specific configuration will not change the base
      action configuration.
      Base action configuration was set during the action creation.
    
    Indirect action list handle defines 2 types of resources:
    • Mutable handle resource can be changed during handle lifespan.
    • Immutable handle resource value is set during handle creation
      and cannot be changed.
    
    There are 2 types of mutable indirect handle contexts:
    • Action mutable context is always shared between all flows
      that referenced indirect actions list handle.
      Action mutable context can be changed by explicit invocation
      of indirect handle update function.
    • Flow mutable context is private to a flow.
      Flow mutable context can be updated by indirect list handle
      flow rule configuration.
    
    flow 1:
     / indirect handle H conf C1 /
                       |       |
                       |       |
                       |       |         flow 2:
                       |       |         / indirect handle H conf C2 /
                       |       |                           |      |
                       |       |                           |      |
                       |       |                           |      |
                =========================================================
                ^      |       |                           |      |
                |      |       V                           |      V
                |    ~~~~~~~~~~~~~~                      ~~~~~~~~~~~~~~~
                |     flow mutable                        flow mutable
                |     context 1                           context 2
                |    ~~~~~~~~~~~~~~                      ~~~~~~~~~~~~~~~
      indirect  |      |                                   |
      action    |      |                                   |
      context   |      V                                   V
                |   -----------------------------------------------------
                |                 action mutable context
                |   -----------------------------------------------------
                v                action immutable context
                =========================================================
    
    Indirect action types - immutable, action / flow mutable, are mutually
    exclusive and depend on the action definition.
    For example:
    • Indirect METER_MARK policy is immutable action member and profile is
      action mutable action member.
    • Indirect METER_MARK flow action defines init_color as flow mutable
      member.
    • Indirect QUOTA flow action does not define flow mutable members.
    
    If indirect list handle was created from a list of actions
    A1 / A2 ... An / END
    indirect list flow action can update Ai flow mutable context in the
    action configuration parameter.
    Indirect list action configuration is and array [C1, C2,  .., Cn]
    where Ci corresponds to Ai in the action handle source.
    Ci configuration element points Ai flow mutable update, or it's NULL
    if Ai has no flow mutable update.
    Indirect list action configuration can be NULL if the action
    has no flow mutable updates.
    
    Template API:
    
    Action template format:
    
            template .. indirect_list handle Htmpl conf Ctmpl ..
            mask     .. indirect_list handle Hmask conf Cmask ..
    
    1 If Htmpl was masked (Hmask != 0), it will be fixed in that template.
      Otherwise, indirect action value is set in a flow rule.
    
    2 If Htmpl and Ctmpl[i] were masked (Hmask !=0 and Cmask[i] != 0),
      Htmpl's Ai action flow mutable context fill be updated to
      Ctmpl[i] values and will be fixed in that template.
    
    Flow rule format:
    
            actions .. indirect_list handle Hflow conf Cflow ..
    
    3 If Htmpl was not masked in actions template, Hflow references an
      action of the same type as Htmpl.
    
    4 Cflow[i] updates handle's Ai flow mutable configuration if
      the Ci was not masked in action template.
    
    Signed-off-by: Gregory Etelson <getelson@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 22.04.2 LTS       
	  Kernel : 5.15.0-60-generic         
	  GCC : 11.3.0-1ubuntu1~22.04        
	  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 22.04.2 LTS       
	  Kernel : 5.15.0-60-generic         
	  GCC : 11.3.0-1ubuntu1~22.04        
	  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