diff options
| -rw-r--r-- | src/dpdk/Makefile | 2 | ||||
| -rw-r--r-- | src/package-list.mk | 4 | ||||
| -rw-r--r-- | test_spec/vswitchperf_ltd.md | 25 |
3 files changed, 28 insertions, 3 deletions
diff --git a/src/dpdk/Makefile b/src/dpdk/Makefile index c6cc7bb1..4e99944b 100644 --- a/src/dpdk/Makefile +++ b/src/dpdk/Makefile @@ -62,6 +62,6 @@ $(WORK_DIR): $(TAG_DONE_FLAG): $(WORK_DIR) $(AT)cd $(WORK_DIR); git checkout $(DPDK_TAG) $(AT)sed -i 's/CONFIG_RTE_BUILD_COMBINE_LIBS=n/CONFIG_RTE_BUILD_COMBINE_LIBS=y/g' $(CONFIG_FILE) - # KNI was causing the 1.6.0 build to fail + $(AT)sed -i 's/CONFIG_RTE_LIBRTE_VHOST=n/CONFIG_RTE_LIBRTE_VHOST=y/g' $(CONFIG_FILE) $(AT)sed -i 's/CONFIG_RTE_LIBRTE_KNI=y /CONFIG_RTE_LIBRTE_KNI=n/g' $(CONFIG_FILE) $(AT)touch $@ diff --git a/src/package-list.mk b/src/package-list.mk index 0e64457b..0dbdbd29 100644 --- a/src/package-list.mk +++ b/src/package-list.mk @@ -6,8 +6,8 @@ # dpdk section # DPDK_URL ?= git://dpdk.org/dpdk DPDK_URL ?= http://dpdk.org/git/dpdk -DPDK_TAG ?= v1.6.0r0 +DPDK_TAG ?= v1.8.0 # OVS section OVS_URL ?= https://github.com/openvswitch/ovs -OVS_TAG ?= v2.3.1 +OVS_TAG ?= da79ce2b71dd879e7f20fdddc715568f6a74185a diff --git a/test_spec/vswitchperf_ltd.md b/test_spec/vswitchperf_ltd.md index 55015629..f63a39e2 100644 --- a/test_spec/vswitchperf_ltd.md +++ b/test_spec/vswitchperf_ltd.md @@ -585,7 +585,32 @@ The following represents possible deployments which can help to determine the pe - Physical → virtual switch → physical. <br/> + - #####Test ID: LTD.Throughput.RFC2544.BackToBackFrames + **Title**: RFC 2544 Back To Back Frames Test + **Prerequisite Test**: N\A + + **Priority**: + + **Description**: + + The aim of this test is to characterize the ability of the DUT to process back-to-back frames. For each frame size previously defined under [Default Test Parameters](#DefaultParams), a burst of traffic is sent to the DUT with the minimum inter-frame gap between each frame. If the number of received frames equals the number of frames that were transmitted, the burst size should be increased and traffic is sent to the DUT again. The value measured is the back-to-back value, that is the maximum burst size the DUT can handle without any frame loss. + + **Expected Result**: + + Tests of back-to-back frames with physical devices have produced unstable results in some cases. All tests should be repeated in multiple test sessions and results stability should be examined. + + **Metrics collected** + + The following are the metrics collected for this test: + + - The back-to-back value, which is the the number of frames in the longest burst that the DUT will handle without the loss of any frames. + + **Deployment scenario**: + + - Physical → virtual switch → physical. + +<br/> [RFC1242]:(http://www.ietf.org/rfc/rfc1242.txt) [RFC2544]:(http://www.ietf.org/rfc/rfc2544.txt) [RFC5481]:(http://www.ietf.org/rfc/rfc5481.txt) |