From: Peng Yuan <yuan.peng@intel.com>
To: dts@dpdk.org
Cc: Peng Yuan <yuan.peng@intel.com>
Subject: [dts] [PATCH]test_plans: remove a case from iavf_fdir_test_plan.rst
Date: Tue, 2 Jun 2020 14:16:52 +0000 [thread overview]
Message-ID: <1591107412-125734-1-git-send-email-yuan.peng@intel.com> (raw)
remove a case from iavf_fdir_test_plan.rst
Signed-off-by: Peng Yuan <yuan.peng@intel.com>
diff --git a/test_plans/iavf_fdir_test_plan.rst b/test_plans/iavf_fdir_test_plan.rst
index 28a1e04..4a07c47 100644
--- a/test_plans/iavf_fdir_test_plan.rst
+++ b/test_plans/iavf_fdir_test_plan.rst
@@ -3251,47 +3251,6 @@ Subcase 8: PF reset VF and delete the rule
8. send matched packets, check them redirected to expected queue with FDIR matched ID.
-Subcase 9: create 2048 rules on VF00 and VF01 and VF10 and VF11 at meantime
----------------------------------------------------------------------------
-
-1. start testpmd on vf00::
-
- ./testpmd -c 0x3 -n 6 -w 86:01.0 --file-prefix=vf00 -- -i --rxq=4 --txq=4
-
- start testpmd on vf01::
-
- ./testpmd -c 0xc -n 6 -w 86:01.1 --file-prefix=vf01 -- -i --rxq=4 --txq=4
-
- start testpmd on vf10::
-
- ./testpmd -c 0x30 -n 6 -w 86:11.0 --file-prefix=vf10 -- -i --rxq=4 --txq=4
-
- start testpmd on vf11::
-
- ./testpmd -c 0xc0 -n 6 -w 86:11.1 --file-prefix=vf11 -- -i --rxq=4 --txq=4
-
-2. create 2048 rules on vf00::
-
- flow create 0 ingress pattern eth / ipv4 src is 192.168.0.20 dst is 192.168.0.0 / end actions queue index 1 / mark / end
- flow create 0 ingress pattern eth / ipv4 src is 192.168.0.20 dst is 192.168.0.1 / end actions queue index 1 / mark / end
- ......
- flow create 0 ingress pattern eth / ipv4 src is 192.168.0.20 dst is 192.168.7.255 / end actions queue index 1 / mark / end
-
- created successfully, check 2048 rules are listed.
- create 2048 rules on vf01/vf10/vf11 at meantime::
-
- flow create 0 ingress pattern eth / ipv4 src is 192.168.0.20 dst is 192.168.0.0 / end actions queue index 1 / mark / end
- flow create 0 ingress pattern eth / ipv4 src is 192.168.0.20 dst is 192.168.0.1 / end actions queue index 1 / mark / end
- ......
- flow create 0 ingress pattern eth / ipv4 src is 192.168.0.20 dst is 192.168.7.255 / end actions queue index 1 / mark / end
-
- all the rules are created successfully.
- check the rule list, there listed 2048 rules.
- send packet to the four vfs, the packets can be redirected to expected queue with mark ID.
-
-3. flush all the rules on four VFs at meantime, there is no error reported.
- send packet to the four vfs, the packets are distributed by RSS without mark ID.
-
Test case: PFCP coverage test
=============================
Subcase 1: PFCP FDIR vlan strip on HW checksum offload check
--
2.14.3
next reply other threads:[~2020-06-02 7:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 14:16 Peng Yuan [this message]
2020-06-03 2:29 ` 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=1591107412-125734-1-git-send-email-yuan.peng@intel.com \
--to=yuan.peng@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).