diff options
author | Yichen Wang <yicwang@cisco.com> | 2017-11-22 16:26:29 -0800 |
---|---|---|
committer | Yichen Wang <yicwang@cisco.com> | 2017-11-24 01:52:53 -0800 |
commit | 1ce98c7510f810a5ee790523a0dcbf429961adda (patch) | |
tree | d29558354fdef0b51a1487fa67ad15022a1c1ad4 /nfvbench/cfg.default.yaml | |
parent | 58d63a026082a7e3207e409d51e919f959627e56 (diff) |
Add support to use vswitch to handle V2V in PVVP SRIOV scenario
1. Add support to use vswitch to handle V2V in PVVP SRIOV scenario
2. Update nfvbenchvm to 0.5:
(1) Update VPP to 17.10;
(2) Update DPDK testpmd to 17.08;
(3) Change kernel to based on longterm lineup;
Change-Id: I944489579a4cd92d17075e80870bbdb32512a150
Signed-off-by: Yichen Wang <yicwang@cisco.com>
Diffstat (limited to 'nfvbench/cfg.default.yaml')
-rw-r--r-- | nfvbench/cfg.default.yaml | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/nfvbench/cfg.default.yaml b/nfvbench/cfg.default.yaml index 83dd5ac..a8bdc2b 100644 --- a/nfvbench/cfg.default.yaml +++ b/nfvbench/cfg.default.yaml @@ -253,6 +253,11 @@ internal_networks: segmentation_id: physical_network: +# In the scenario of PVVP + SRIOV, there is choice of how the traffic will be +# handled in the middle network. The default (false) will use vswitch, while +# SRIOV can be used by toggling below setting. +use_sriov_middle_net: false + # EXT chain only. Names of edge networks which will be used to send traffic via traffic generator. external_networks: left: 'nfvbench-net0' @@ -400,4 +405,4 @@ factory_class: 'BasicFactory' # Custom label added for every perf record generated during this run. # Can be overriden by --user-label -user_label:
\ No newline at end of file +user_label: |