From: Taha Sami <taha.sami@dreambigsemi.com>
To: "users@dpdk.org" <users@dpdk.org>,
"akozyrev@nvidia.com" <akozyrev@nvidia.com>,
"suanmingm@nvidia.com" <suanmingm@nvidia.com>
Cc: "asafp@nvidia.com" <asafp@nvidia.com>
Subject: meter_mark action not working with NVIDIA Cx6-Dx
Date: Mon, 27 Feb 2023 06:50:19 +0000 [thread overview]
Message-ID: <BY5PR22MB1986BCF112F090566053A8E290AF9@BY5PR22MB1986.namprd22.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5007 bytes --]
Hello,
We are trying to test the meter mark feature with the testpmd but we are observing some unusual results. We are trying to send different color packets to different queues but we are not seeing the desired results
Supporting INFO
MT2892 Family [ConnectX-6 Dx]
Driver: mlx5_core
Version: 5.8-1.1.2
Firmware-version: 22.35.2000 (MT_0000000436)
dpdk- 22.11
Here are our test steps
Step 1: Configuring meter_mark in testpmd:
sudo ./build/app/dpdk-testpmd -l 0-3 -n 4 -a 0000:4:00.0,dv_flow_en=2 --file-prefix ts -- -i --disable-rss --txq=9 –rxq=9
port stop 0
port configure
flow configure 0 queues_number 9 queues_size 256 meters_number 1
Pattern template configure
flow pattern_template 0 create pattern_template_id 2 relaxed true ingress template eth dst is 00:16:3e:31:15:c3 / end
flow pattern_template 0 create pattern_template_id 4 relaxed true ingress template meter color is green / end
flow pattern_template 0 create pattern_template_id 5 relaxed true ingress template meter color is yellow / end
flow pattern_template 0 create pattern_template_id 6 relaxed true ingress template meter color is red / end
Action Template configure
flow actions_template 0 create actions_template_id 1 template jump group 1 / end mask jump group 1 / end
flow actions_template 0 create actions_template_id 2 template meter_mark mtr_profile 0 mtr_color_mode 1
mtr_init_color green mtr_state 1 / jump group 2 / end mask meter_mark mtr_profile 0 mtr_color_mode 1 mtr_init_color green mtr_state 1 / jump group 2 / end
flow actions_template 0 create actions_template_id 4 template queue index 2 / end mask queue index 2 / end
flow actions_template 0 create actions_template_id 5 template queue index 6 / end mask queue index 6 / end
flow actions_template 0 create actions_template_id 6 template drop / end mask drop / end
Template Table creation
flow template_table 0 create table_id 1 group 0 ingress rules_number 10 pattern_template 2 actions_template 1
flow template_table 0 create table_id 2 group 1 ingress rules_number 10 pattern_template 2 actions_template 2
flow template_table 0 create table_id 4 group 2 ingress rules_number 10 pattern_template 4 actions_template 4
flow template_table 0 create table_id 5 group 2 ingress rules_number 10 pattern_template 5 actions_template 5
flow template_table 0 create table_id 6 group 2 ingress rules_number 10 pattern_template 6 actions_template 6
port start 0
profile creation for meter mark
add port meter profile trtcm_rfc2698 0 0 120 250 20 3000 0
Flow queue creation
flow queue 0 create 0 template_table 1 pattern_template 0 actions_template 0 postpone 0 pattern eth dst is 00:16:3e:31:15:c3 / end actions drop / end
flow queue 0 create 0 template_table 2 pattern_template 0 actions_template 0 postpone 0 pattern eth dst is 00:16:3e:31:15:c3 / end actions drop / end
flow queue 0 create 0 template_table 4 pattern_template 0 actions_template 0 postpone 0 pattern meter color is green / end actions drop / end
flow queue 0 create 0 template_table 5 pattern_template 0 actions_template 0 postpone 0 pattern meter color is yellow / end actions drop / end
flow queue 0 create 0 template_table 6 pattern_template 0 actions_template 0 postpone 0 pattern meter color is red / end actions drop / end
Push/Pull operation
flow push 0 queue 0
Queue #0 operations pushed
flow pull 0 queue 0
Queue #0 pulled 2 operations (0 failed, 2 succeeded)
After pulling the flow rules it was observed that only 2 rules were successfully pulled
initially, after sending 2000 packets of 64 bytes from pktgen we saw only 1 packet received on queue 2 even though only 2 rules were successfully pushed and pulled from the nic
------- Forward Stats for RX Port= 0/Queue= 2 -> TX Port= 0/Queue= 2 -------
RX-packets: 1 TX-packets: 1 TX-dropped: 0
---------------------- Forward statistics for port 0 ----------------------
RX-packets: 1 RX-dropped: 0 RX-total: 1
TX-packets: 1 TX-dropped: 0 TX-total: 1
----------------------------------------------------------------------------
+++++++++++++++ Accumulated forward statistics for all ports+++++++++++++++
RX-packets: 1 RX-dropped: 0 RX-total: 1
TX-packets: 1 TX-dropped: 0 TX-total: 1
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
after again sending 2000 packets of 64 bytes
---------------------- Forward statistics for port 0 ----------------------
RX-packets: 0 RX-dropped: 0 RX-total: 0
TX-packets: 0 TX-dropped: 0 TX-total: 0
----------------------------------------------------------------------------
+++++++++++++++ Accumulated forward statistics for all ports+++++++++++++++
RX-packets: 0 RX-dropped: 0 RX-total: 0
TX-packets: 0 TX-dropped: 0 TX-total: 0
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Regards,
Taha
[-- Attachment #2: Type: text/html, Size: 9052 bytes --]
next reply other threads:[~2023-02-28 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 6:50 Taha Sami [this message]
2023-02-28 2:18 ` Alexander Kozyrev
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=BY5PR22MB1986BCF112F090566053A8E290AF9@BY5PR22MB1986.namprd22.prod.outlook.com \
--to=taha.sami@dreambigsemi.com \
--cc=akozyrev@nvidia.com \
--cc=asafp@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=users@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).