summaryrefslogtreecommitdiffstats
path: root/src/tests
AgeCommit message (Expand)AuthorFilesLines
2018-06-19tcp: optimize tcp outputFlorin Coras1-1/+2
2018-06-04fix usage string missing argJerome Tollet1-1/+1
2018-05-19tcp_echo: support multiple connectionsFlorin Coras1-218/+250
2018-05-09session: cleanup session tx functionFlorin Coras2-49/+79
2018-04-18udp/session: refactor to support dgram modeFlorin Coras1-172/+303
2018-03-07tls: enforce certificate verificationFlorin Coras1-45/+49
2018-03-05tls: add stop listen handlerFlorin Coras1-11/+102
2018-02-14session: support local sessions and deprecate redirectsFlorin Coras2-44/+87
2018-02-05session: segment manager refactorFlorin Coras2-2/+2
2018-01-27session: use clib rwlocks instead of custom implementationFlorin Coras1-1/+1
2018-01-25session: add support for memfd segmentsFlorin Coras2-251/+313
2018-01-22svm: queue sub: Add conditional timed waitMohsin Kazmi2-4/+4
2018-01-09api: refactor vlibmemoryFlorin Coras2-40/+26
2018-01-05sock api: add infra for bootstrapping shm clientsFlorin Coras1-39/+73
2017-12-15apps: refactor uri and update build infraFlorin Coras2-0/+2452
2017-06-08LISP: add NSH supportFilip Tehlar1-3/+73
2017-05-03Fix vnet unit testsFilip Tehlar3-32/+82
2017-04-25LISP: clean DP when deleting locators in useFilip Tehlar1-2/+2
2017-03-30Clean up more Debian packaging symbol warningsDave Barach2-2/+0
2016-12-28Reorganize source tree to use single autotools instanceDamjan Marion4-0/+1232
| Description | | ---------------------- | ------------------------------------------- | | build-data | Build metadata | | build-root | Build output directory | | doxygen | Documentation generator configuration | | dpdk | DPDK patches and build infrastructure | | @ref extras/libmemif | Client library for memif | | @ref src/examples | VPP example code | | @ref src/plugins | VPP bundled plugins directory | | @ref src/svm | Shared virtual memory allocation library | | src/tests | Standalone tests (not part of test harness) | | src/vat | VPP API test program | | @ref src/vlib | VPP application library | | @ref src/vlibapi | VPP API library | | @ref src/vlibmemory | VPP Memory management | | @ref src/vnet | VPP networking | | @ref src/vpp | VPP application | | @ref src/vpp-api | VPP application API bindings | | @ref src/vppinfra | VPP core library | | @ref src/vpp/api | Not-yet-relocated API bindings | | test | Unit tests and Python test harness | ## Getting started In general anyone interested in building, developing or running VPP should consult the [VPP wiki](https://wiki.fd.io/view/VPP) 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: ./extras/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 `extras/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 end-user-oriented information. Also see @subpage dev_doc for developer notes. Visit the [VPP wiki](https://wiki.fd.io/view/VPP) for details on more advanced building strategies and other development notes. ## Test Framework There is PyDoc generated documentation available for the VPP test framework. See @ref test_framework_doc for details.