test suite reviews and discussions
 help / color / mirror / Atom feed
From: Peng Yuan <yuan.peng@intel.com>
To: dts@dpdk.org
Cc: pengyuan <yuan.peng@intel.com>
Subject: [dts] [PATCH]test_plans: Add 4*25 NIC description for cvl_fdir_test_plan.rst
Date: Mon, 22 Jun 2020 09:51:37 +0000	[thread overview]
Message-ID: <1592819497-17496-1-git-send-email-yuan.peng@intel.com> (raw)

From: pengyuan <yuan.peng@intel.com>

Add 4*25 NIC description for cvl_fdir_test_plan.rst

Signed-off-by: pengyuan <yuan.peng@intel.com>

diff --git a/test_plans/cvl_fdir_test_plan.rst b/test_plans/cvl_fdir_test_plan.rst
index 12e5041..254bb53 100644
--- a/test_plans/cvl_fdir_test_plan.rst
+++ b/test_plans/cvl_fdir_test_plan.rst
@@ -2463,6 +2463,16 @@ Subcase 1: port stop/port start/port reset
 
 8. verify matched packet can be still redirected to queue 1 with FDIR matched ID=0x0.
 
+9. add a new rule::
+
+    flow create 0 ingress pattern eth dst is 00:11:22:33:44:55 / ipv4 src is 192.168.0.22 dst is 192.168.0.23 / end actions queue index 2 / mark id 1 / end
+
+10. list the rule and send matched packet::
+
+    sendp([Ether(dst="00:11:22:33:44:55")/IP(src="192.168.0.22",dst="192.168.0.23") / Raw('x' * 80)],iface="enp175s0f0")
+
+   check the packet are redirected to queue 2 with FDIR matched ID=0x1
+
 Subcase 2: add/delete rules
 ---------------------------
 
@@ -2579,6 +2589,9 @@ Subcase 3: delete rules
 
 Subcase 4: max rules
 --------------------
+This case is designed based on 2*100G NIC.
+If 4*25 NIC, each PF port has 512 fdir rules guaranteed.
+So there can be created 14848 fdir rules on 1 PF port.
 
 1. create 15360 rules on port 0::
 
-- 
2.14.3


             reply	other threads:[~2020-06-22  2:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22  9:51 Peng Yuan [this message]
2020-06-28  6:35 ` 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=1592819497-17496-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).