From: Xueqin Lin <xueqin.lin@intel.com>
To: dts@dpdk.org
Cc: Xueqin Lin <xueqin.lin@intel.com>
Subject: [dts] [PATCH] test_plans/unit_tests_lpm: add lpm perf and lpm6 perf cases
Date: Tue, 8 Jan 2019 20:37:02 -0500 [thread overview]
Message-ID: <1546997822-35288-1-git-send-email-xueqin.lin@intel.com> (raw)
Signed-off-by: Xueqin Lin <xueqin.lin@intel.com>
---
test_plans/unit_tests_lpm_test_plan.rst | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
diff --git a/test_plans/unit_tests_lpm_test_plan.rst b/test_plans/unit_tests_lpm_test_plan.rst
index cf6978b..4fa9248 100644
--- a/test_plans/unit_tests_lpm_test_plan.rst
+++ b/test_plans/unit_tests_lpm_test_plan.rst
@@ -77,3 +77,31 @@ The steps to run the unit test manually are as follow::
The final output of the test has to be "Test OK"
+
+
+====================
+Unit Tests: LPM_perf
+====================
+
+This section explains how to run the unit tests for LPM performance.
+The steps to run the unit test manually are as follow::
+
+ # make -C ./app/test/
+ # ./app/test/test -n 1 -c ffff
+ RTE>> lpm_perf_autotest
+
+The final output of the test has to be "Test OK"
+
+
+=========================
+Unit Tests: LPM_ipv6_perf
+=========================
+
+This section explains how to run the unit tests for LPM IPv6
+performance. The steps to run the unit test manually are as follow::
+
+ # make -C ./app/test/
+ # ./app/test/test -n 1 -c ffff
+ RTE>> lpm6_perf_autotest
+
+The final output of the test has to be "Test OK"
--
2.5.5
next reply other threads:[~2019-01-09 7:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 1:37 Xueqin Lin [this message]
2019-01-11 2:13 ` 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=1546997822-35288-1-git-send-email-xueqin.lin@intel.com \
--to=xueqin.lin@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).