From: Yan Xia <yanx.xia@intel.com>
To: dts@dpdk.org
Cc: Yan Xia <yanx.xia@intel.com>
Subject: [dts] [PATCH V1 1/2] test_plans/ftag_test_plan: remove ftag_test_plan
Date: Thu, 20 May 2021 11:41:56 +0800 [thread overview]
Message-ID: <20210520034157.10877-1-yanx.xia@intel.com> (raw)
Signed-off-by: Yan Xia <yanx.xia@intel.com>
---
test_plans/ftag_test_plan.rst | 110 ----------------------------------
1 file changed, 110 deletions(-)
delete mode 100644 test_plans/ftag_test_plan.rst
diff --git a/test_plans/ftag_test_plan.rst b/test_plans/ftag_test_plan.rst
deleted file mode 100644
index 413d0cee..00000000
--- a/test_plans/ftag_test_plan.rst
+++ /dev/null
@@ -1,110 +0,0 @@
-.. Copyright (c) <2016-2017>, Intel Corporation
- All rights reserved.
-
- Redistribution and use in source and binary forms, with or without
- modification, are permitted provided that the following conditions
- are met:
-
- - Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
-
- - Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in
- the documentation and/or other materials provided with the
- distribution.
-
- - Neither the name of Intel Corporation nor the names of its
- contributors may be used to endorse or promote products derived
- from this software without specific prior written permission.
-
- THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
- FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
- COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
- INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
- (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
- SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
- HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
- STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
- ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
- OF THE POSSIBILITY OF SUCH DAMAGE.
-
-===========================
-FM10k FTAG Forwarding Tests
-===========================
-
-FM10000 supports the addition of a Fabric Tag (FTAG) to carry special
-information between Switches, between Switch and PCIe Host Interface or
-between Switch and Tunneling Engines. This tag is essential for a set of
-switches to behave like one switch (switch aggregation).
-
-The FTAG is placed at the beginning of the frame. The case will validate
-packet forwarding function based on FTAG.
-
-Prerequisites
-=============
-
-Turn on CONFIG_RTE_LIBRTE_FM10K_FTAG_FWD in common_linuxapp configuration file.
-Startup testpoint and export Port0 and Port1's GLORT ID.
-
-Strip port logic value from mac table information.
-There's the sample output from RubyRapid. From the output, port0's logic
-value is 4122 and port1's logic value is 4123::
-
- <0>% show mac table all
- MAC Mode FID1 FID2 Type Value Trig ...
- ------------------ --------- ---- ---- ------ ------ -----
- 00:00:00:00:01:01 Dynamic 1 NA Local 1 1
- a0:36:9f:60:b6:6e Static 1 NA PF/VF 4506 1
- a0:36:9f:60:b6:68 Static 1 NA PF/VF 4123 1
- 00:00:00:00:01:00 Dynamic 1 NA Local 1 1
- a0:36:9f:60:b6:66 Static 1 NA PF/VF 4122 1
-
-
-Strip port glort ID from stacking information.
-There's the sample output from RubyRapid. Logic port0's GLORT ID is 0x4000.
-Logic port1's GLORT ID is 0x4200::
-
- show stacking logical-port all
- <0>% show stacking logical-port all
-
- SW GLORT LOGICAL PORT PORT TYPE
- ---- ----- --------------- ---------
- ...
- 0 0x4000 4122 ?
- 0 0x4200 4123 ?
-
-Add port's GLORT ID into environment variables::
-
- export PORT1_GLORT=0x4200
- export PORT0_GLORT=0x4000
-
-Test Case: Ftag forwarding unit test
-====================================
-
-1. port 0 pci 85:00.0, port 1 pci 87:00.0,start test application::
-
- ./x86_64-native-linuxapp-gcc/app/test -c f -n 4 -w 0000:85:00.0,enable_ftag=1 -w 0000:87:00.0,enable_ftag=1
-
-2. Run FTAG test function::
-
- RTE>>fm10k_ftag_autotest
-
-3. Send one packet to Port0 and verify packet with ftag forwarded to Port1::
-
- Receive 1 packets on port 0
- test for FTAG RX passed
- Send out 1 packets with FTAG on port 0
- Receive 1 packets on port 1
- test for FTAG TX passed
- Test OK
-
-4. Send one packet to Port1 and verify packet with ftag forwarded to Port0::
-
- Receive 1 packets on port 0
- test for FTAG RX passed
- Send out 1 packets with FTAG on port 0
- Receive 1 packets on port 1
- test for FTAG TX passed
- Test OK
--
2.17.1
next reply other threads:[~2021-05-20 3:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 3:41 Yan Xia [this message]
2021-05-20 3:41 ` [dts] [PATCH V1 2/2] tests/ftag: remove TestSuite_ftag Yan Xia
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=20210520034157.10877-1-yanx.xia@intel.com \
--to=yanx.xia@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).