automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: rongweil@nvidia.com
Subject: |SUCCESS|dpdk-next-net-mlx|be5e6a96a0| Intel-Testing
Date: 03 Sep 2025 14:54:30 -0700	[thread overview]
Message-ID: <0b0228$58ou46@orviesa005-auth.jf.intel.com> (raw)

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


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

DPDK git repo: dpdk-next-net-mlx
commit be5e6a96a0595f8afde6ba27639791aa87a89761
Author: Rongwei Liu <rongweil@nvidia.com>
Date:   Fri Aug 29 08:35:32 2025 +0300

    net/mlx5: fix probe optimization race condition
    
    With dedicated RDMA link monitor, there are two threads
    which can update the IB device port information.
    
    Add a new flag to avoid the race condition. Update should
    go through RDMA link monitor once ready.
    
    Current logic is:
    1. Update all port information in probing thread.
    2. Probe thread initiates the dedicated rdma monitor thread.
       Once ready, port information update will be handled by this thread.
    3. Next probing won't trigger PMD port information update.
    
    No lock is required.
    
    Fixes: 51fb5c40c826 ("common/mlx5: optimize device probing")
    Cc: stable@dpdk.org
    
    Signed-off-by: Rongwei Liu <rongweil@nvidia.com>
    Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>

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

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
	virtio_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/virtio_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


OS : Ubuntu 22.04.5 LTS       
Kernel : 6.8.0-40-generic         
GCC : 11.4.0-1ubuntu1~22.04.2        
NIC : Ethernet Controller E810-C for SFP         
Target : x86_64-native-linuxapp-gcc      

	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|
	+-------------+---------------------------+-------+


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      

	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|
	+-------------+---------------------------+-------+


DPDK STV team

             reply	other threads:[~2025-09-03 21:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-03 21:54 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-09-02 21:49 sys_stv
2025-09-02  8:43 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='0b0228$58ou46@orviesa005-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=rongweil@nvidia.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).