diff options
| author |   Billy O'Mahony <billy.o.mahony@intel.com> | 2015-07-20 11:59:51 +0100 |
|---|---|---|
| committer |   Maryam Tahhan <maryam.tahhan@intel.com> | 2015-08-05 09:40:18 +0000 |
| commit | d476ee6b6db3968443d6d82d5ffef8acefb3dccb (patch) | |
| tree | e5e08417397d96720d0f10448baa79f9c677df61 | |
| parent | 37f74b50178fc458d9e1bc9fff1cd8bcdd9ada8d (diff) | |
test_spec: Clarify LTD.Throughput.RFC2889.BroadcastFrameForwarding
Make changes based on comments from review at VSPERF weekly call 2015-07-15.
JIRA: VSPERF-2
Change-Id: I3742518edaea09c9a32a71c9cccc3c4c09fd4598
Signed-off-by: Billy O'Mahony<billy.o.mahony@intel.com>
Reviewed-by: Al Morton <acmorton@att.com>
Reviewed-by: Eugene Snider <Eugene.Snider@huawei.com>
Reviewed-by: Maryam Tahhan <maryam.tahhan@intel.com>
Reviewed-by: Gurpreet Singh <gurpreet.singh@spirent.com>
Reviewed-by: Tv Rao <tv.rao@freescale.com>
| -rwxr-xr-x | test_spec/vswitchperf_ltd.md | 13 |
1 files changed, 12 insertions, 1 deletions
diff --git a/test_spec/vswitchperf_ltd.md b/test_spec/vswitchperf_ltd.md index 07d49dc9..947d49d0 100755 --- a/test_spec/vswitchperf_ltd.md +++ b/test_spec/vswitchperf_ltd.md @@ -1103,13 +1103,24 @@ The starting point for defining the suite of tests for benchmarking the performa The aim of this test is to determine the maximum forwarding rate of the DUT when forwarding broadcast traffic. For each frame previously defined under [Default Test Parameters](#DefaultParams), the traffic should be set up as broadcast traffic. The traffic throughput of the DUT should be measured. + The test should be conducted with at least 4 physical ports on the DUT. The number of ports used MUST be recorded. + + As broadcast involves forwarding a single incoming packet to several destinations, the latency of a single packet is defined as the average of the latencies for each of the broadcast destinations. + + The incoming packet is transmitted on each of the other physical ports, it is not transmitted on the port on which it was received. The test MAY be conducted using different broadcasting ports to uncover any performance differences. + **Expected Result**: - **Metrics collected** + **Metrics collected**: The following are the metrics collected for this test: - The forwarding rate of the DUT when forwarding broadcast traffic. + - The minimum, average & maximum packets latencies observed. + + **Deployment scenario**: + + - Physical → virtual switch 3x physical. <br/> - #####Test ID: LTD.MemoryBandwidth.RFC2544.0PacketLoss.Scalability |