automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: dsosnowski@nvidia.com
Subject: |SUCCESS|dpdk-next-net-mlx|d686476f7e| Intel-Testing
Date: 31 Aug 2025 14:56:46 -0700	[thread overview]
Message-ID: <7ef141$56s8mo@fmviesa003-auth.fm.intel.com> (raw)

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


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

DPDK git repo: dpdk-next-net-mlx
commit d686476f7ecc3a7d0952890e2a3a996e1c34d515
Author: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date:   Tue Aug 19 13:27:42 2025 +0200

    net/mlx5: fix indirect age action handling
    
    Indirect AGE flow actions can be created either through synchronous
    or asynchronous flow API.
    mlx5 PMD stores the queue used to create that action to support
    strict queueing. When action is created through synchronous API
    invalid queue index is stored instead.
    
    Whenever a flow rule is created with indirect AGE and
    direct COUNT flow actions, PMD allocates a HW counter for ageing
    that flow rule during rule creation.
    During allocation of the counter a queue index is needed
    to select a proper counter pool cache.
    
    In case when indirect AGE action created through synchronous API
    was used in that case, the associated queue index was used
    to select pool cache. Since queue index was invalid, PMD crashed.
    
    Counter can be allocated using the index of currently used queue and
    it does not have to match the queue used to create AGE action.
    
    This patch fixes the crash by using the index of currently used queue
    for counter allocation.
    
    This patch also adds missing validation for synchronous
    and asynchronous AGE flow action creation:
    
    - If strict queueing is disabled, only synchronous creation is allowed.
    - If strict queueing is enabled, only asynchronous creation is allowed.
    
    PMD documentation is updated accordingly.
    
    It also updates validation of synchronous query
    of aged flow rules in regards to strict queueing.
    When strict queueing is enabled, synchronous query is rejected.
    This aligns PMD behavior with API description.
    
    Fixes: 04a4de756e14 ("net/mlx5: support flow age action with HWS")
    Cc: michaelba@nvidia.com
    Cc: stable@dpdk.org
    
    Signed-off-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
    Acked-by: Bing Zhao <bingz@nvidia.com>
    Acked-by: Raslan Darawsheh <rasland@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-08-31 21:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-31 21:56 sys_stv [this message]
2025-09-01  9:12 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='7ef141$56s8mo@fmviesa003-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=dsosnowski@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).