From: Jiale Song <songx.jiale@intel.com>
To: dts@dpdk.org
Cc: Jiale Song <songx.jiale@intel.com>
Subject: [dts] [PATCH V1] tests/cvl_fdir: add mark id
Date: Fri, 12 Nov 2021 16:03:03 +0800 [thread overview]
Message-ID: <1636704183-158693-1-git-send-email-songx.jiale@intel.com> (raw)
after the packet comes in, it hits the switch rule first and then the fdir rule. the final action
is the superposition of the two. the priority of switch is higher than fdir, so it goes to the
switch queue, but it still contains the fdir mark action
Signed-off-by: Jiale Song <songx.jiale@intel.com>
---
test_plans/cvl_fdir_test_plan.rst | 4 ++--
tests/TestSuite_cvl_fdir.py | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/test_plans/cvl_fdir_test_plan.rst b/test_plans/cvl_fdir_test_plan.rst
index 4c4526d8..ed1214f9 100644
--- a/test_plans/cvl_fdir_test_plan.rst
+++ b/test_plans/cvl_fdir_test_plan.rst
@@ -3589,7 +3589,7 @@ set "--log-level=ice,7", then check::
sendp([Ether(dst="00:11:22:33:44:55")/IP(src="192.168.0.20",dst="192.168.0.21") /UDP(sport=22, dport=23)/ Raw('x' * 80)],iface="enp175s0f0", count=10)
the two packets are both redirected to queue 1 with mark ID 1.
- then create MAC_IPV4_UDP flow, it is set to switch filter::
+ then create MAC_IPV4_UDP flow, it is set to switch filter with mark ID 1::
flow create 0 ingress pattern eth / ipv4 dst is 192.168.0.21 / udp src is 22 dst is 23 / end actions queue index 2 / end
@@ -3610,7 +3610,7 @@ set "--log-level=ice,7", then check::
flow create 0 ingress pattern eth / ipv4 dst is 192.168.0.21 / end actions queue index 1 / end
- send same packet, it is redirected to queue 1, because the packet match switch filter first.
+ send same packet, it is redirected to queue 1 with mark ID 1, because the packet match switch filter first.
Test case: count/query
diff --git a/tests/TestSuite_cvl_fdir.py b/tests/TestSuite_cvl_fdir.py
index d4cb90ce..529be0e8 100644
--- a/tests/TestSuite_cvl_fdir.py
+++ b/tests/TestSuite_cvl_fdir.py
@@ -3007,7 +3007,7 @@ class TestCVLFdir(TestCase):
out = self.send_pkts_getouput(pkts=pkts[0])
rfc.check_mark(out, pkt_num=1, check_param={"port_id": 0, "queue": 1,"mark_id":1}, stats=True)
out = self.send_pkts_getouput(pkts=pkts[1])
- rfc.check_mark(out, pkt_num=1, check_param={"port_id": 0, "queue": 2}, stats=True)
+ rfc.check_mark(out, pkt_num=1, check_param={"port_id": 0, "queue": 2,"mark_id":1}, stats=True)
rule3 = "flow create 0 ingress pattern eth / ipv4 dst is 192.168.0.21 / udp src is 22 dst is 23 / end actions queue index 2 / mark id 1 / end"
rule4 = "flow create 0 ingress pattern eth / ipv4 dst is 192.168.0.21 / end actions queue index 1 / end"
--
2.17.1
next reply other threads:[~2021-11-12 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 8:03 Jiale Song [this message]
2021-11-23 14:36 ` Tu, Lijuan
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=1636704183-158693-1-git-send-email-songx.jiale@intel.com \
--to=songx.jiale@intel.com \
--cc=dts@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).