summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorRadek Zetik <radekx.zetik@intel.com>2016-01-25 12:22:46 +0000
committerMaryam Tahhan <maryam.tahhan@intel.com>2016-01-25 16:15:47 +0000
commitcdda1e1aaaae6c22a592980cabd6f301d661f737 (patch)
tree672f7b104e43ed15b884297d7e66793de297ceba /docs
parente35cbd393b2c2df7648ac5ba73544069983acd51 (diff)
VSPERF docs: Patches for Design Document
Routing Table Figure has an odd description for the table#1 description. Connectivity to the DUT is assumed, could provide example directions. Suggest a new section. JIRA: VSPERF-178 JIRA: VSPERF-179 Change-Id: I38e48034a9029d4a8969affdddef5b281dc8eba3 Signed-off-by: Radek Zetik <radekx.zetik@intel.com> Reviewed-by: Maryam Tahhan <maryam.tahhan@intel.com> Reviewed-by: Brian Castelli <brian.castelli@spirent.com> Reviewed-by: Al Morton <acmorton@att.com> Reviewed-by: Tv Rao <tv.rao@freescale.com> (cherry picked from commit 11ea896d3dee85a79316c57838adef8807784359)
Diffstat (limited to 'docs')
-rwxr-xr-xdocs/design/vswitchperf_design.rst13
1 files changed, 11 insertions, 2 deletions
diff --git a/docs/design/vswitchperf_design.rst b/docs/design/vswitchperf_design.rst
index b8988458..1d27d55c 100755
--- a/docs/design/vswitchperf_design.rst
+++ b/docs/design/vswitchperf_design.rst
@@ -12,6 +12,15 @@ deployment scenarios and so on.
Usage
=====
+Example Connectivity to DUT
+---------------------------
+
+Establish connectivity to the VSPERF DUT Linux host, such as the DUT in Pod 3,
+by following the steps in `Testbed POD3
+<https://wiki.opnfv.org/get_started/pod_3_-_characterize_vswitch_performance>`__
+
+The steps cover booking the DUT and establishing the VSPERF environment.
+
Example Command Lines
---------------------
@@ -226,8 +235,8 @@ Frame Modification requirements.
|
|
v
- +--------------+ table#1 - Routing table. Flows to route packets between
- | | ports goes here.
+ +--------------+ table#1 - Routing table. Flow entries to forward
+ | | packets between ports goes here.
| Table 1 | The chosen port is communicated to subsequent tables by
| | setting the metadata value to the egress port number.
| | Generally this table is set-up by by the