diff options
author | 2017-10-05 06:44:17 +0000 | |
---|---|---|
committer | 2017-10-05 06:44:17 +0000 | |
commit | bde80dd0127ff65de738085a73832834e2ab1902 (patch) | |
tree | 1b6f2f3db9254921ea6978ad0ac1ad71a6b4bad8 /docs/testing/user/userguide | |
parent | 9d2900035923bf307477c5b4b8dc423ba1b2086f (diff) | |
parent | 08ae2a2bbc7883cc242102cf70813ab2911d4d5d (diff) |
Merge "doc_review: Review docs for accuracy and grammar"
Diffstat (limited to 'docs/testing/user/userguide')
-rw-r--r-- | docs/testing/user/userguide/integration.rst | 2 | ||||
-rw-r--r-- | docs/testing/user/userguide/testusage.rst | 12 |
2 files changed, 8 insertions, 6 deletions
diff --git a/docs/testing/user/userguide/integration.rst b/docs/testing/user/userguide/integration.rst index 83b29da6..249a03c4 100644 --- a/docs/testing/user/userguide/integration.rst +++ b/docs/testing/user/userguide/integration.rst @@ -457,7 +457,7 @@ To run GENEVE decapsulation tests: Executing Tunnel encapsulation+decapsulation tests -------------------------------------------------- -The OVS DPDK encapsulation_decapsulation tests requires IPs, MAC addresses, +The OVS DPDK encapsulation/decapsulation tests requires IPs, MAC addresses, bridge names and WHITELIST_NICS for DPDK. The test cases can test the tunneling encap and decap without using any ingress diff --git a/docs/testing/user/userguide/testusage.rst b/docs/testing/user/userguide/testusage.rst index 4d3528d0..20c30a40 100644 --- a/docs/testing/user/userguide/testusage.rst +++ b/docs/testing/user/userguide/testusage.rst @@ -20,6 +20,8 @@ support in VSPERF includes: Traffic generator modules. - Moongen software traffic generator. Requires a separate machine running moongen to execute packet generation. +- T-Rex software traffic generator. Requires a separate machine running T-Rex + Server to execute packet generation. If you want to use another traffic generator, please select the :ref:`trafficgen-dummy` generator. @@ -475,7 +477,7 @@ For example: * vSwitch tests with DPDK or without DPDK support to verify impact of VF usage on vSwitch performance -* tests without vSwitch, where traffic is forwared directly +* tests without vSwitch, where traffic is forwarded directly between VF interfaces by packet forwarder (e.g. testpmd application) * tests without vSwitch, where VM accesses VF interfaces directly by PCI-passthrough_ to measure raw VM throughput performance. @@ -486,11 +488,11 @@ Using QEMU with PCI passthrough support ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Raw virtual machine throughput performance can be measured by execution of PVP -test with direct access to NICs by PCI passthrough. To execute VM with direct +test with direct access to NICs by PCI pass-through. To execute VM with direct access to PCI devices, enable vfio-pci_. In order to use virtual functions, SRIOV-support_ must be enabled. -Execution of test with PCI passthrough with vswitch disabled: +Execution of test with PCI pass-through with vswitch disabled: .. code-block:: console @@ -498,9 +500,9 @@ Execution of test with PCI passthrough with vswitch disabled: --vswitch none --vnf QemuPciPassthrough pvp_tput Any of supported guest-loopback-application_ can be used inside VM with -PCI passthrough support. +PCI pass-through support. -Note: Qemu with PCI passthrough support can be used only with PVP test +Note: Qemu with PCI pass-through support can be used only with PVP test deployment. .. _guest-loopback-application: |