diff options
| author |   Maryam Tahhan <maryam.tahhan@intel.com> | 2015-08-12 12:53:35 +0100 |
|---|---|---|
| committer | Maryam Tahhan <maryam.tahhan@intel.com> | 2015-08-12 12:56:41 +0000 |
| commit | b5de49062df3a39152a799d2c1677287622b107d (patch) | |
| tree | 740a95244e6ec3b3fcbdb6cdf55dfbc77e1fef29 | |
| parent | 96c257c2738d8f60e42733c49a0ccb337cd2223a (diff) | |
TestSpec: Add actions to flow Classification
Clarify that a flow has an associated action and isn't simply packets
with matching header fields.
Change-Id: Iffa7ae121049d8ec798f937082a733ef520e9d05
JIRA: VSPERF-49
Signed-off-by: Maryam Tahhan <maryam.tahhan@intel.com>
Reviewed-by: Al Morton <acmorton@att.com>
| -rw-r--r-- | test_spec/vswitchperf_ltd.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/test_spec/vswitchperf_ltd.md b/test_spec/vswitchperf_ltd.md index 96987567..11426239 100644 --- a/test_spec/vswitchperf_ltd.md +++ b/test_spec/vswitchperf_ltd.md @@ -369,7 +369,7 @@ The following represents possible deployments which can help to determine the pe **Note**: For throughput tests unless stated otherwise, test configurations should ensure that traffic traverses the installed flows through the switch, i.e. flows are installed and have an appropriate time out that doesn't expire before packet transmission starts. #####Flow Classification: -Virtual switches group packets into flows by processing and matching particular header fields in the packet or frame, or by matching packets based on the input ports into the vSwitch. Thus a flow is considered to be a sequence of packets that have a shared set of header field values or have arrived on the same port. Performance results can vary based on the parameters the vSwitch uses to match for a flow. The recommended flow classification parameters for any vSwitch performance tests are: the input port, the source IP address, the destination IP address and the Ethernet protocol type field. It is essential to increase the flow time-out time on a vSwitch before conducting any performance tests that do not measure the flow set-up time. Normally the first packet of a particular flow will install the flow in the vSwitch which adds an additional latency, subsequent packets of the same flow are not subject to this latency if the flow is already installed on the vSwitch. +Virtual switches classify packets into flows by processing and matching particular header fields in the packet/frame and/or the input port where the packets/frames arrived. The vSwitch then carries out an action on the group of packets that match the classification parameters. Thus a flow is considered to be a sequence of packets that have a shared set of header field values or have arrived on the same port and have the same action applied to them. Performance results can vary based on the parameters the vSwitch uses to match for a flow. The recommended flow classification parameters for L3 vSwitch performance tests are: the input port, the source IP address, the destination IP address and the Ethernet protocol type field. It is essential to increase the flow time-out time on a vSwitch before conducting any performance tests that do not measure the flow set-up time. Normally the first packet of a particular flow will install the flow in the vSwitch which adds an additional latency, subsequent packets of the same flow are not subject to this latency if the flow is already installed on the vSwitch. #####Test Priority Tests will be assigned a priority in order to determine which tests should be implemented immediately and which tests implementations can be deferred. |