From 400c276d192d280cf74f09b2e8b2234057b56de3 Mon Sep 17 00:00:00 2001 From: Maryam Tahhan Date: Mon, 24 Aug 2015 14:05:15 +0100 Subject: docs: Migrate Docs to RST format and new dir docs/ Migrate all existing VSPERF documentation to a new directory called docs/ and convert to ReStructuredText format. It's recommended that any doc changes in the future are tested with: http://rst.ninjs.org/. Change-Id: I18aa574b1259986502bde4ceef1fae7c6a5c1f33 JIRA: VSPERF-60 Signed-off-by: Maryam Tahhan Reviewed-by: Al Morton Reviewed-by: Eugene Snider Reviewed-by: Gurpreet Singh Reviewed-by: Tv Rao All Programs -> IXIA -> IxNetwork -> IxNetwork_$(VER_NUM) -> IxNetwork TCL Server) - - Right click on IxNetwork TCL Server, select properties - - Under shortcut tab in the Target dialogue box make sure there is the argument "-tclport xxxx" where xxxx is your port number (take note of this port number you will need it for the 10_custom.conf file). - ![Alt text](TCLServerProperties.png) - - Hit Ok and start the TCL server application - -## Cloning and building src dependencies -In order to run VSPERF, you will need to download DPDK and OVS. You can do this manually and build them in a preferred location, or you could use vswitchperf/src. The vswitchperf/src directory contains makefiles that will allow you to clone and build the libraries that VSPERF depends on, such as DPDK and OVS. To clone and build simply: - -```bash -cd src -make -``` - -VSPERF can be used with OVS without DPDK support. In this case you have to specify path to the kernel sources by WITH_LINUX parameter: - -```bash -cd src -make WITH_LINUX=/lib/modules/`uname -r`/build -``` - -To build DPDK and OVS for PVP testing, use: - -```bash -make VHOST_USER=y -``` - -To delete a src subdirectory and its contents to allow you to re-clone simply use: - -```bash -make cleanse -``` - -## Configure the `./conf/10_custom.conf` file - -The supplied `10_custom.conf` file must be modified, as it contains configuration items for which there are no reasonable default values. - -The configuration items that can be added is not limited to the initial contents. Any configuration item mentioned in any .conf file in `./conf` directory can be added and that item will be overridden by the custom -configuration value. - -## Using a custom settings file - -Alternatively a custom settings file can be passed to `vsperf` via the `--conf-file` argument. - -```bash -./vsperf --conf-file ... -``` - -Note that configuration passed in via the environment (`--load-env`) or via another command line argument will override both the default and your custom configuration files. This "priority hierarchy" can be described like so (1 = max priority): - -1. Command line arguments -2. Environment variables -3. Configuration file(s) - ---- - -## Executing tests -Before running any tests make sure you have root permissions by adding the following line to /etc/sudoers: -``` -username ALL=(ALL) NOPASSWD: ALL -``` -username in the example above should be replaced with a real username. - -To list the available tests: - -```bash -./vsperf --list-tests -``` - -To run a group of tests, for example all tests with a name containing -'RFC2544': - -```bash -./vsperf --conf-file=user_settings.py --tests="RFC2544" -``` - -To run all tests: - -```bash -./vsperf --conf-file=user_settings.py -``` - -Some tests allow for configurable parameters, including test duration (in -seconds) as well as packet sizes (in bytes). - -```bash -./vsperf --conf-file user_settings.py - --tests RFC2544Tput - --test-param "rfc2544_duration=10;packet_sizes=128" -``` - -For all available options, check out the help dialog: - -```bash -./vsperf --help -``` - ---- - -[installation instructions]: installation.md - -- cgit 1.2.3-korg