From: Peng Yuan <yuan.peng@intel.com>
To: dts@dpdk.org
Cc: Peng Yuan <yuan.peng@intel.com>
Subject: [dts] [PATCH]test_plans: correct typo errors
Date: Tue, 18 Feb 2020 11:20:21 +0800 [thread overview]
Message-ID: <1581996021-43375-1-git-send-email-yuan.peng@intel.com> (raw)
correct typo errors in qos_sched_test_plan.rst, and remove two subports cases.
Signed-off-by: Peng Yuan <yuan.peng@intel.com>
diff --git a/test_plans/qos_sched_test_plan.rst b/test_plans/qos_sched_test_plan.rst
index 8675406..0340eee 100644
--- a/test_plans/qos_sched_test_plan.rst
+++ b/test_plans/qos_sched_test_plan.rst
@@ -308,7 +308,7 @@ Test Case: best effort TC12
2. The traffic manage setting is configured in profile.cfg.
Set flows with QinQ inner vlan ID=0, which represents pipe 0.
- Set IP dst address from 10.0.0.12~10.0.0.4, which enter queue12~queue14,
+ Set IP dst address from 10.0.0.12~10.0.0.14, which enter queue12~queue14,
mapping TC12.
Frame size=70bytes.
Send rate is 100% linerate.
@@ -591,6 +591,9 @@ the default mastercore 1 and the RX, WT and TX cores only.
Test Case: Two Subports, different pipe profiles, different number of pipes I
=============================================================================
+*Note: the sample can't be set to two subports,
+ so the two supports case can't be verified.*
+
1. Configure the profile.cfg file with two subports, two different pipe
profiles and different number of pipes::
@@ -636,6 +639,9 @@ Test Case: Two Subports, different pipe profiles, different number of pipes I
Test Case: Two Subports, different pipe profiles, different number of pipes II
==============================================================================
+*Note: the sample can't be set to two subports,
+ so the two supports case can't be verified.*
+
1. Configure the profile.cfg file the same with last case I.
2. This example uses a single packet flow configuration
@@ -666,7 +672,7 @@ Test Case: Redistribution of unused pipe BW to other pipes within the same subpo
which creates one RX thread on lcore 5 reading from port 0
and a worker thread on lcore 7 writing to port 1::
- ./qos_sched -l 1,2,5,7 -n 4 -- -i --pfc "0,1,2,5,7" --cfg ../profile.cfg
+ ./qos_sched -l 1,2,5,7 -n 4 -- -i --pfc "0,1,2,5,7" --cfg ../profile_ov.cfg
3. The generator settings:
Configure 4 flows:
--
2.7.4
next reply other threads:[~2020-02-18 3:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 3:20 Peng Yuan [this message]
2020-02-18 7:06 ` 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=1581996021-43375-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).