Age | Commit message (Collapse) | Author | Files | Lines |
|
In the LTD, some of the tests with "Throughput" in the title are not actually
testing throughput in the data path.
Since the test names are used by TOIT/VSPERF to group similar tests for batch
execution, it's important that the names accurately represent the test methods
and metrics measured.
JIRA: VSPERF-98
Change-Id: I620ddc0779232f2dd325379005faba8692fea18c
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>
|
|
A few of the tests should call out a prerequisite.
LTD.MemoryBandwidth.RFC2544.0PacketLoss.Scalability
and
LTD.Scalability.RFC2544.0PacketLoss
are examples.
JIRA: VSPERF-107
Change-Id: I1ca653ac765f9494b48759764103dfc9d42a42f1
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>
|
|
LTD.Throughput.RFC2544.Profile refers to the metric "maximum forwarding rate"
but implies that this is the zero% loss rate, which would be the Throughput
level (MFR is usually higher than Throughput, because MFR allows losses).
It may be that MFR and Throughput are just interchanged in the last two
paragraphs of the description.
JIRA: VSPERF-110
Change-Id: I4f36fd4ce66f2f4ebee4f60a11ad03adfb2b3b7c
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>
|
|
The following text in the Description needs to be formatted as a list in .RST:
Furthermore: - the ratio of reads to writes should be recorded.
JIRA: VSPERF-109
Change-Id: I3b6c819d1ac07cc466c747d3552cbcc4de5f34bf
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>
|
|
In the RFC 2889 Broadcast rate testing, four test ports are required.
One of the ports is connected to the test device, so it can send
broadcast frames and listen for miss-routed frames.
JIRA: VSPERF-103
Change-Id: I5ee3d20c71d7debf6c7b09fc094f72b2d4c10684
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>
|
|
The RFC 2889 Address Learning and Cache Capacity tests require
a listening port to check for flooded frames.
JIRA: VSPERF-74
Change-Id: I7b4d2461e819d01d642c9c4d95b938dfbe056f2c
Signed-off-by: Al Morton <acmorton@att.com>
Reviewed-by: Maryam Tahhan <maryam.tahhan@intel.com>
|
|
The Current list of fixed frame sizes need to be augmented with
IMIX Traffic Profiles in the test framework.
JIRA: VSPERF-100
Change-Id: I97425c09c1d692bae56f2518d479b83a282eb7d1
Signed-off-by: Al Morton <acmorton@att.com>
Reviewed-by: Maryam Tahhan <maryam.tahhan@intel.com>
|
|
The RFC 2889 tests require Full Mesh on multiple ports.
Modify the bunny-ears fig to show this (and address -99 in the process)
JIRA: VSPERF-99
JIRA: VSPERF-101
Change-Id: Id67cb5ef6748c83858a90033534f960874614c06
Signed-off-by: Al Morton <acmorton@att.com>
Reviewed-by: Maryam Tahhan <maryam.tahhan@intel.com>
|
|
TODO: Reorganize documentation into properly named subfolders
TODO: Add logos to documentation (see index.rst for example)
Note you can see the results of this change via a link in the gerrit
comments below
NOTE: The merge job for your project has not been enabled, this code
will not go to the artifacts page upon a merge. you can merge it and
work on it in your own time, please contact me to enable the merge
(the merge job will make this documentation avaliable to the public on
artifacts.opnfv.org)
JIRA:RELENG-15
Change-Id: I3f3d8c9d7fceae90e0ed824b66bdaf7a8ea66328
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|