summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAl Morton <acmorton@att.com>2015-09-07 00:44:50 +0100
committerMaryam Tahhan <maryam.tahhan@intel.com>2015-10-16 09:28:16 +0000
commit6f35ae4f20e2f47fae569b29907fa77102ee9ee2 (patch)
tree14426efde318f5e80079fcf589a35dac262eb8c4
parentd3963c641b755deaad01422b7d8c0009fa1fbdc6 (diff)
test_spec: Need deployment scenario in RFC2889 Forwarding Rate test
The RFC 2889 Forwarding Rate test requires a Deployment Scenario Section - was missing. JIRA: VSPERF-102 Change-Id: Iaf661a6bbb9ad52f23147f9444f23d96a82ceb2d Signed-off-by: Al Morton <acmorton@att.com> Reviewed-by: Maryam Tahhan <maryam.tahhan@intel.com> Reviewed-by: Billy O'Mahony<billy.o.mahony@intel.com> Reviewed-by: Gene Snider <eugene.snider@huawei.com>
-rwxr-xr-xdocs/to-be-reorganized/vswitchperf_ltd.rst8
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/to-be-reorganized/vswitchperf_ltd.rst b/docs/to-be-reorganized/vswitchperf_ltd.rst
index 33162bf4..3ffd23e3 100755
--- a/docs/to-be-reorganized/vswitchperf_ltd.rst
+++ b/docs/to-be-reorganized/vswitchperf_ltd.rst
@@ -1468,6 +1468,14 @@ Test ID: LTD.Throughput.RFC2889.MaxForwardingRate
- CPU and memory utilization may also be collected as part of this
test, to determine the vSwitch's performance footprint on the system.
+ **Deployment scenario**:
+
+ - Physical → virtual switch → physical. Note: Full mesh tests with
+ multiple ingress and egress ports are a key aspect of RFC 2889
+ benchmarks, and scenarios with both 2 and 4 ports should be tested.
+ In any case, the number of ports used must be reported.
+
+
Test ID: LTD.Throughput.RFC2889.ForwardPressure
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
**Title**: RFC2889 Forward Pressure Test