From: Ke Xu <ke1.xu@intel.com>
To: dts@dpdk.org
Cc: lijuan.tu@intel.com, Ke Xu <ke1.xu@intel.com>,
Jin Ling <jin.ling@intel.com>
Subject: [DTS][PATCH V1 2/3] test_plans/ice_dcf_acl_filter: remove redundant white space
Date: Wed, 30 Nov 2022 11:53:57 +0800 [thread overview]
Message-ID: <20221130035358.98410-3-ke1.xu@intel.com> (raw)
In-Reply-To: <20221130035358.98410-1-ke1.xu@intel.com>
Signed-off-by: Jin Ling <jin.ling@intel.com>
Signed-off-by: Ke Xu <ke1.xu@intel.com>
---
test_plans/ice_dcf_acl_filter_test_plan.rst | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/test_plans/ice_dcf_acl_filter_test_plan.rst b/test_plans/ice_dcf_acl_filter_test_plan.rst
index f047598d..893c1078 100644
--- a/test_plans/ice_dcf_acl_filter_test_plan.rst
+++ b/test_plans/ice_dcf_acl_filter_test_plan.rst
@@ -522,14 +522,14 @@ while we can create 256 ipv4-udp/ipv4-tcp/ipv4-sctp rules at most.
sendp([Ether(dst="00:01:23:45:67:89")/IP(src="192.168.1.0", dst="192.168.100.2")/UDP(sport=8010,dport=8017)/Raw(load='X'*30)], iface="enp134s0f1")
check the packet can't be received by VF1. stop the forward::
-
+
---------------------- Forward statistics for port 1 ----------------------
RX-packets: 0 RX-dropped: 0 RX-total: 0
TX-packets: 0 TX-dropped: 0 TX-total: 0
----------------------------------------------------------------------------
8. delete the rule 256 and 257::
-
+
flow destroy 0 rule 256
flow destroy 0 rule 257
@@ -542,7 +542,7 @@ while we can create 256 ipv4-udp/ipv4-tcp/ipv4-sctp rules at most.
9. create the rule in the step6 again,
check the rule can be created as acl rule successfully.
list the rules, there are rule 0-256 listed.
-
+
10.send packet2 again, check the packet dropped. stop the forward::
---------------------- Forward statistics for port 1 ----------------------
@@ -565,7 +565,7 @@ Test Case 6: max entry number ipv4-other
flow create 0 ingress pattern eth / ipv4 src spec 192.168.0.1 src mask 255.255.255.255 / end actions drop / end
3. create 64 ipv4-other ACL rules::
-
+
flow create 0 ingress pattern eth / ipv4 src spec 192.168.1.1 src mask 255.255.0.255 / end actions drop / end
flow create 0 ingress pattern eth / ipv4 src spec 192.168.1.2 src mask 255.255.0.255 / end actions drop / end
flow create 0 ingress pattern eth / ipv4 src spec 192.168.1.3 src mask 255.255.0.255 / end actions drop / end
@@ -599,12 +599,12 @@ Test Case 6: max entry number ipv4-other
sendp([Ether(dst="00:01:23:45:67:89")/IP(src="192.168.0.2", dst="192.168.1.2")/Raw(load='X'*30)], iface="enp134s0f1")
check the packet can't be received by vf1. stop forward::
-
+
---------------------- Forward statistics for port 1 ----------------------
RX-packets: 0 RX-dropped: 0 RX-total: 0
TX-packets: 0 TX-dropped: 0 TX-total: 0
----------------------------------------------------------------------------
-
+
8. delete the rule 64 and 65::
flow destroy 0 rule 64
--
2.25.1
next prev parent reply other threads:[~2022-11-30 3:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 3:53 [DTS][PATCH V1 0/3] update test plans and tests to support represented port action and port representor action from deprecated vf action in ice_dcf_acl_filter Ke Xu
2022-11-30 3:53 ` [DTS][PATCH V1 1/3] test_plans/ice_dcf_acl_filter: update test plan to support represented port action from deprecated vf action Ke Xu
2022-11-30 3:53 ` Ke Xu [this message]
2022-11-30 3:53 ` [DTS][PATCH V1 3/3] tests/ice_dcf_acl_filter: " Ke Xu
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=20221130035358.98410-3-ke1.xu@intel.com \
--to=ke1.xu@intel.com \
--cc=dts@dpdk.org \
--cc=jin.ling@intel.com \
--cc=lijuan.tu@intel.com \
/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).