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 V2 2/2] test_plans/cvl_limit_value_test: adapt to chapman beach for test plan
Date: Fri,  9 Apr 2021 12:49:32 +0000	[thread overview]
Message-ID: <20210409124932.31720-3-qinx.sun@intel.com> (raw)
In-Reply-To: <20210409124932.31720-1-qinx.sun@intel.com>

add description about maximum rules for chapman beach card in this plan

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

diff --git a/test_plans/cvl_limit_value_test_test_plan.rst b/test_plans/cvl_limit_value_test_test_plan.rst
index 242eb9a7..9cb0cf09 100644
--- a/test_plans/cvl_limit_value_test_test_plan.rst
+++ b/test_plans/cvl_limit_value_test_test_plan.rst
@@ -154,6 +154,8 @@ Subcase 1: 14336 rules on 1 vf
 
 Subcase 2: 14336 rules on 2 vfs of 2pfs
 ---------------------------------------
+For chapman beach 100g*2 NIC, if 2 vfs generated by one pf port,they will share 14336 rules,
+if 2 vfs generated by 2 pf port, each vf can create 14336 rules at most.
 
 1. start testpmd on vf00::
 
@@ -195,6 +197,8 @@ each pf can create 512 rules at least in 4 ports card.
 there are 14k rules shared by pfs and vfs.
 so 1 pf and 2 vfs can create 15360 rules at most on 2 ports card.
 1 pf and 2 vfs can create 14848 rules at most on 4 ports card.
+if hardware is chapman beach 100g*2, 1 pf can create 2048 rules,vfs generated by the same pf share 14336 rules,so
+this card can create (2048 + 14336)*2=32768 rules.
 
 1. create 1025 rules on pf0::
 
@@ -265,6 +269,8 @@ there are 14k rules shared by pfs and vfs.
 so 1 pf and 2 vfs can create 15360 rules at most on 2 ports card.
 1 pf and 2 vfs can create 14848 rules at most on 4 ports card.
 so if create 15360/14848 rules on 1 pf, there can't create rule on vf successfully.
+if hardware is chapman beach 100g*2, 1 pf can create 2048 rules,vfs generated by the same pf share 14336 rules,
+so if create 16384 rules on pf1,check failed to create rule on vf00 and vf10(vf00 and vf10 generated by pf1).
 
 1. create 15360 rules on pf0::
 
-- 
2.17.1


  parent reply	other threads:[~2021-04-09  4:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 12:49 [dts] [PATCH V2 0/2] adapt to chapman beach platform sunqin
2021-04-09 12:49 ` [dts] [PATCH V2 1/2] tests/cvl_limit_value_test: adapt to chapman beach sunqin
2021-04-09 12:49 ` sunqin [this message]
2021-04-12  2:17 ` [dts] [PATCH V2 0/2] adapt to chapman beach platform Sun, QinX
2021-04-13  1:21 ` 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=20210409124932.31720-3-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).