From d3963c641b755deaad01422b7d8c0009fa1fbdc6 Mon Sep 17 00:00:00 2001
From: Al Morton <acmorton@att.com>
Date: Fri, 2 Oct 2015 02:18:09 +0100
Subject: [PATCH] test_spec: LTD: Add Caution for Scaleability Address
Time-out.
LTD.Scalability.RFC2544.0PacketLoss needs to add the caution that
all flows must be learned before running Throughput testing,
and no flows can be allowed to time-out during the test.
JIRA: VSPERF-108
Change-Id: I95ae20a978b7af660b358450e67ce60939b0b7c1
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>
---
docs/to-be-reorganized/vswitchperf_ltd.rst | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/docs/to-be-reorganized/vswitchperf_ltd.rst b/docs/to-be-reorganized/vswitchperf_ltd.rst
index 4e194d0c..33162bf4 100755
--- a/docs/to-be-reorganized/vswitchperf_ltd.rst
+++ b/docs/to-be-reorganized/vswitchperf_ltd.rst
@@ -1701,7 +1701,17 @@ Test ID: LTD.Scalability.RFC2544.0PacketLoss
- 64,000
- Max supported number of flows.
- The maximum 0% packet loss throughput should be determined in a manner
+ This test will be conducted under two conditions following the
+ establishment of all flows as required by RFC 2544, regarding the flow
+ expiration time-out:
+
+ 1) The time-out never expires during each trial.
+
+ 2) The time-out expires for all flows periodically. This would require a
+ short time-out compared with flow re-appearance for a small number of
+ flows, and may not be possible for all flow conditions.
+
+ The maximum 0% packet loss Throughput should be determined in a manner
identical to LTD.Throughput.RFC2544.PacketLossRatio.
**Expected Result**:
--
2.16.6