Gitiles
Code Review Sign In
gerrit.nordix.org / fdio / vpp / 9225dee9655ce607130f9bab5472441b72e25858
commit9225dee9655ce607130f9bab5472441b72e25858[log] [tgz]
authorKlement Sekera <ksekera@cisco.com>Mon Dec 12 08:36:58 2016 +0100
committerOle Trøan <otroan@employees.org>Fri Dec 16 08:09:40 2016 +0000
tree6438ea39bf2b14eeca70770890165497ee146d30
parentcc53285baf2c3a45b95e22dd66c8592d634568ee [diff]
make test: improve robustness and performance

Introduce an API which asserts empty capture for interface.
Throw exception in old API if the capture does not exist, thus
making it clear if the test expects packets to arrive or not.
Improve performance by not doing sleeps after starting the packet
generator, rather lazily deleting captures when needed.
Fix wrong usage of packet.show() in various tests.

Change-Id: I456cb23316eef99b3f35f80344fe595c4db9a21c
Signed-off-by: Klement Sekera <ksekera@cisco.com>
12 files changed
tree: 6438ea39bf2b14eeca70770890165497ee146d30
  1. build-data/
  2. build-root/
  3. doxygen/
  4. dpdk/
  5. g2/
  6. gmod/
  7. perftool/
  8. plugins/
  9. svm/
  10. test/
  11. vlib/
  12. vlib-api/
  13. vnet/
  14. vpp/
  15. vpp-api/
  16. vpp-api-test/
  17. vppapigen/
  18. vppinfra/
  19. .gitignore
  20. .gitreview
  21. LICENSE
  22. Makefile
  23. README.md
  24. RELEASE.md
README.md

Vector Packet Processing

Introduction

The VPP platform is an extensible framework that provides out-of-the-box production quality switch/router functionality. It is the open source version of Cisco's Vector Packet Processing (VPP) technology: a high performance, packet-processing stack that can run on commodity CPUs.

The benefits of this implementation of VPP are its high performance, proven technology, its modularity and flexibility, and rich feature set.

For more information on VPP and its features please visit the FD.io website and What is VPP? pages.

Changes

Details of the changes leading up to this version of VPP can be found under @ref release_notes.

Directory layout

Directory nameDescription
build-dataBuild metadata
build-rootBuild output directory
doxygenDocumentation generator configuration
dpdkDPDK patches and build infrastructure
g2Event log visualization tool
perftoolPerformance tool
@ref pluginsVPP bundled plugins directory
@ref svmShared virtual memory allocation library
testUnit tests
@ref vlibVPP application library source
@ref vlib-apiVPP API library source
@ref vnetVPP networking source
@ref vppVPP application source
@ref vpp-apiVPP application API source
vppapigenVPP API generator source
vpp-api-testVPP API test program source
@ref vppinfraVPP core library source

(If the page you are viewing is not generated by Doxygen then ignore any @@ref labels in the above table.)

Getting started

In general anyone interested in building, developing or running VPP should consult the VPP wiki for more complete documentation.

In particular, readers are recommended to take a look at [Pulling, Building, Running, Hacking, Pushing](https://wiki.fd.io/view/VPP/Pulling,_Building,_Run ning,_Hacking_and_Pushing_VPP_Code) which provides extensive step-by-step coverage of the topic.

For the impatient, some salient information is distilled below.

Quick-start: On an existing Linux host

To install system dependencies, build VPP and then install it, simply run the build script. This should be performed a non-privileged user with sudo access from the project base directory:

./build-root/vagrant/build.sh

If you want a more fine-grained approach because you intend to do some development work, the Makefile in the root directory of the source tree provides several convenience shortcuts as make targets that may be of interest. To see the available targets run:

make

Quick-start: Vagrant

The directory build-root/vagrant contains a VagrantFile and supporting scripts to bootstrap a working VPP inside a Vagrant-managed Virtual Machine. This VM can then be used to test concepts with VPP or as a development platform to extend VPP. Some obvious caveats apply when using a VM for VPP since its performance will never match that of bare metal; if your work is timing or performance sensitive, consider using bare metal in addition or instead of the VM.

For this to work you will need a working installation of Vagrant. Instructions for this can be found [on the Setting up Vagrant wiki page] (https://wiki.fd.io/view/DEV/Setting_Up_Vagrant).

More information

Several modules provide documentation, see @subpage user_doc for more information.

Visit the VPP wiki for details on more advanced building strategies and development notes.