1b696ac9b3
See .../src/vnet/classify/trace_classify.h for the business end of the scheme. It would be best to hash pkts, prefetch buckets, and do the primary table lookups two at a time. The inline as given works, but perf tuning will be required. "At least it works..." Add "classify filter" debug cli, for example: classify filter mask l3 ip4 src dst \ match l3 ip4 dst 192.168.2.10 src 192.168.1.10 Add "pcap rx | tx trace ... filter" to use the current classify filter chain Patch includes sphinx documentation and doxygen tags. Next step: device-driver integration Type: feature Signed-off-by: Dave Barach <dave@barachs.net> Change-Id: I05b1358a769f61e6d32470e0c87058f640486b26 (cherry picked from commit 9137e5400699bed9f7c0095187839a8b38273100)
Building VPP Documents These instructions show how the VPP documentation sources are built. To build your files, you can either Create a Virtual Environment using virtualenv, which installs all the required applications for you. Create a Virtual Environment using virtualenv ============================ For more information on how to use the Python virtual environment check out https://packaging.python.org/guides/installing-using-pip-and-virtualenv Get the Documents ------------------------------ For example start with a clone of the vpp. $ git clone https://gerrit.fd.io/r/vpp $ cd vpp Install the virtual environment ---------------------------------------------- $ python -m pip install --user virtualenv $ python -m virtualenv env $ source env/bin/activate $ pip install -r docs/etc/requirements.txt $ cd docs Which installs all the required applications into it's own, isolated, virtual environment, so as to not interfere with other builds that may use different versions of software. Build the html files ---------------------------- Be sure you are in your vpp/docs directory, since that is where Sphinx will look for your conf.py file, and build the documents into an index.html file $ make html View the results ------------------------ If there are no errors during the build process, you should now have an index.html file in your vpp/docs/_build/html directory, which you can then view in your browser.