Gitiles
Code Review Sign In
gerrit.nordix.org / fdio / vpp / 86be48773c1833129317a3a0d6fe8165eb69ac3f
commit86be48773c1833129317a3a0d6fe8165eb69ac3f[log] [tgz]
authorDamjan Marion <damarion@cisco.com>Tue May 24 23:19:11 2016 +0200
committerDamjan Marion <damarion@cisco.com>Mon Jun 13 19:04:12 2016 +0200
treeff6ddc2933e9a18aba8e3e841fb6f495bc7efe4a
parenta38c3df5fd2bf1bf8b3389e882f6dcd5ac533202 [diff]
Explicity specify IP address type for format_ip46_address function

Change-Id: I3379517535a98a7a5fbd3173503f288a81378821
Signed-off-by: Damjan Marion <damarion@cisco.com>
7 files changed
tree: ff6ddc2933e9a18aba8e3e841fb6f495bc7efe4a
  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
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.

Directory layout.

Directory nameDescription
build-dataBuild metadata
build-rootBuild output directory
doxygenDocumentation generator configuration
dpdkDPDK patches and build infrastructure
g2Event log visualization tool
gmodperf related?
perftoolPerformance tool
sample-pluginA sample plugin
@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.

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