automatic DPDK test reports
 help / color / mirror / Atom feed
* [dpdk-test-report]|SUCCESS | dpdk-next-net-mlx|f97189ae50| Intel-Testing
@ 2023-02-26 14:45 sys_stv
  0 siblings, 0 replies; only message in thread
From: sys_stv @ 2023-02-26 14:45 UTC (permalink / raw)
  To: test-report
  Cc: lijuan.tu, chenyux.huang, Rongwei Liu, Raslan Darawsheh, daxuex.gao

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


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

DPDK git repo: dpdk-next-net-mlx

commit f97189ae50cb531fa86ef9c0de22bb0af2797d82
Author: Rongwei Liu <rongweil@nvidia.com>
Date:   Wed Feb 15 14:03:45 2023 +0200

    net/mlx5: support live migration
    
    When a DPDK application must be upgraded,
    the traffic downtime should be shortened as much as possible.
    During the migration time, the old application may stay alive
    while the new application is starting and being configured.
    
    In order to optimize the switch to the new application,
    the old application may need to be aware of the presence
    of the new application being prepared.
    This is achieved with a new API allowing the user to change the
    new application state to standby and active later.
    
    The added function is trying to apply the new mode to all probed
    mlx5 ports. To make this API simple and easy to use,
    the same flags have to be accepted by all devices.
    
    This is the scenario of operations in the old and new applications:
    .       device: already configured by the old application
    .       new:    start as active
    .       new:    probe the same device
    .       new:    set as standby
    .       new:    configure the device
    .       device: has configurations from old and new applications
    .       old:    clear its device configuration
    .       device: has only 1 configuration from new application
    .       new:    set as active
    .       device: downtime for connecting all to the new application
    .       old:    shutdown
    
    The active mode means network handling configurations are programmed
    to the HW immediately, and no behavior changed. This is the default state.
    The standby mode means configurations are queued in the HW.
    If there is no application with active mode,
    any configuration is effective immediately.
    
    Signed-off-by: Rongwei Liu <rongweil@nvidia.com>
    Acked-by: Viacheslav Ovsiienko <viacheslavo@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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2023-02-26 14:45 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-26 14:45 [dpdk-test-report]|SUCCESS | dpdk-next-net-mlx|f97189ae50| Intel-Testing sys_stv

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).