diff options
Diffstat (limited to 'docs/to-be-reorganized/vswitchperf_ltd.rst')
| -rw-r--r-- | docs/to-be-reorganized/vswitchperf_ltd.rst | 11 |
1 files changed, 8 insertions, 3 deletions
diff --git a/docs/to-be-reorganized/vswitchperf_ltd.rst b/docs/to-be-reorganized/vswitchperf_ltd.rst index d4d61787..ccba2131 100644 --- a/docs/to-be-reorganized/vswitchperf_ltd.rst +++ b/docs/to-be-reorganized/vswitchperf_ltd.rst @@ -443,6 +443,11 @@ Physical port → vSwitch → VNF → vSwitch → VNF → vSwitch → physical p diagram above (with 2 sending and 2 receiving ports, though all ports could be used bi-directionally). +**Note:** When Deployment Scenarios are used in RFC 2889 address learning +or cache capacity testing, an additional port from the vSwitch must be +connected to the test device. This port is used to listen for flooded +frames. + 2.2.3 General Methodology: -------------------------- To establish the baseline performance of the virtual switch, tests would @@ -1544,7 +1549,7 @@ Test ID: LTD.Throughput.RFC2889.AddressCachingCapacity **Deployment scenario**: - - Physical → virtual switch → physical. + - Physical → virtual switch → 2 x physical (one receiving, one listening). Test ID: LTD.Throughput.RFC2889.AddressLearningRate ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -1568,7 +1573,7 @@ Test ID: LTD.Throughput.RFC2889.AddressLearningRate learning rate can be obtained. **Expected Result**: It may be worthwhile to report the behaviour when - operating beyond address capacity - some DUTS may be more friendly to + operating beyond address capacity - some DUTs may be more friendly to new addresses than others. **Metrics collected**: @@ -1579,7 +1584,7 @@ Test ID: LTD.Throughput.RFC2889.AddressLearningRate **Deployment scenario**: - - Physical → virtual switch → physical. + - Physical → virtual switch → 2 x physical (one receiving, one listening). Test ID: LTD.Throughput.RFC2889.ErrorFramesFiltering ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |