test suite reviews and discussions
 help / color / mirror / Atom feed
From: sunqin <qinx.sun@intel.com>
To: dts@dpdk.org
Cc: sunqin <qinx.sun@intel.com>
Subject: [dts] [PATCH V1] test_plans/cvl_limit_value_test add title for test plan
Date: Mon, 23 Nov 2020 14:06:06 +0000	[thread overview]
Message-ID: <20201123140606.6139-1-qinx.sun@intel.com> (raw)

Add title for cvl_limit_value_test plan

Signed-off-by: sunqin <qinx.sun@intel.com>
---
 test_plans/cvl_limit_value_test_test_plan.rst | 20 ++++++++++++-------
 1 file changed, 13 insertions(+), 7 deletions(-)

diff --git a/test_plans/cvl_limit_value_test_test_plan.rst b/test_plans/cvl_limit_value_test_test_plan.rst
index 4c141a17..8c8402e9 100644
--- a/test_plans/cvl_limit_value_test_test_plan.rst
+++ b/test_plans/cvl_limit_value_test_test_plan.rst
@@ -30,7 +30,12 @@
    ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
    OF THE POSSIBILITY OF SUCH DAMAGE.
 
+========================
+CVL Limit Value Test
+========================
 
+Description
+===========
 
 Supported function type
 -----------------------
@@ -51,7 +56,6 @@ Supported action type
     mark
     mark/rss
 
-
 Prerequisites
 =============
 
@@ -103,13 +107,14 @@ Prerequisites
     >>> from scapy.contrib.mpls import *
 
 Test case: Max number
-=====================
+======================
+
 All the max number cases are designed based on 2*100G NIC.
 If the hardware is 4*25G NIC, the guaranteed rule number of PF is 512.
 So in subcase 3 and subcase 4, there can be created at most 14848 rules on 1pf and 2vfs.
 
 Subcase 1: 14336 rules on 1 vf
-------------------------------
+-------------------------------
 
 1. create 14336 rules on vf00::
 
@@ -183,6 +188,7 @@ Subcase 2: 14336 rules on 2 vfs of 2pfs
 
 Subcase 3: 1025 rules on 1pf and 14335 rules on 2vfs
 ----------------------------------------------------
+
 each pf can create 1024 rules at least in 2 ports card.
 each pf can create 512 rules at least in 4 ports card.
 there are 14k rules shared by pfs and vfs.
@@ -249,8 +255,9 @@ so 1 pf and 2 vfs can create 15360 rules at most on 2 ports card.
 
 8. verify matched packet received without FDIR matched ID.
 
-Subcase 3: 15360 rules on 1pf and 0 rules on 2vfs
+Subcase 4: 15360 rules on 1pf and 0 rules on 2vfs
 -------------------------------------------------
+
 each pf can create 1024 rules at least in 2 ports card.
 each pf can create 512 rules at least in 4 ports card.
 there are 14k rules shared by pfs and vfs.
@@ -321,7 +328,6 @@ so if create 15360/14848 rules on 1 pf, there can't create rule on vf successful
 9. send matched packet to vf00, it can be redirected to queue 1 with FDIR matched ID=0x0.
    send matched packet to vf10, it can be redirected to queue 1 with FDIR matched ID=0x0.
 
-
 Test case: Stress test
 ======================
 
@@ -436,7 +442,7 @@ Prerequisites
     ./testpmd -c 0xff -n 6 -w 86:00.0 -w 86:00.1 --log-level="ice,7" -- -i --portmask=0xff --rxq=64 --txq=64 --port-topology=loop
 
 Test case: add/delete rules
----------------------------
+============================
 
 1. create two rules::
 
@@ -591,4 +597,4 @@ create a total of 32563 switch filter rules on a DCF.
      testpmd> flow list 0
 
    check the rules not exist in the list.
-   send 32563 matched packets, check the packets are not to port 1.
\ No newline at end of file
+   send 32563 matched packets, check the packets are not to port 1.
-- 
2.17.1


             reply	other threads:[~2020-11-23  5:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23 14:06 sunqin [this message]
2020-11-23  5:33 ` Sun, QinX
2020-11-26  7:46 ` 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=20201123140606.6139-1-qinx.sun@intel.com \
    --to=qinx.sun@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).