docs: better docs, mv doxygen to sphinx

[vpp.git] / docs / aboutvpp / scalar-vs-vector-packet-processing.rst

diff --git a/docs/whatisvpp/scalar-vs-vector-packet-processing.rst b/docs/aboutvpp/scalar-vs-vector-packet-processing.rst
similarity index 97%
rename from docs/whatisvpp/scalar-vs-vector-packet-processing.rst
rename to docs/aboutvpp/scalar-vs-vector-packet-processing.rst
index ffa54a3..173efec 100644 (file)
--- a/docs/whatisvpp/scalar-vs-vector-packet-processing.rst
+++ b/docs/aboutvpp/scalar-vs-vector-packet-processing.rst
@@ -19,7 +19,7 @@ time: an interrupt handling function takes a single packet from a Network
 Interface, and processes it through a set of functions: fooA calls fooB calls
 fooC and so on.
 
-.. code-block:: none 
+.. code-block:: none
 
    +---> fooA(packet1) +---> fooB(packet1) +---> fooC(packet1)
    +---> fooA(packet2) +---> fooB(packet2) +---> fooC(packet2)
@@ -45,14 +45,14 @@ handling function takes the vector of packets from a Network Interface, and
 processes the vector through a set of functions: fooA calls fooB calls fooC and
 so on.
 
-.. code-block:: none 
+.. code-block:: none
 
    +---> fooA([packet1, +---> fooB([packet1, +---> fooC([packet1, +--->
                packet2,             packet2,             packet2,
                ...                  ...                  ...
                packet256])          packet256])          packet256])
 
-This approach fixes: 
+This approach fixes:
 
 * The I-cache thrashing problem described above, by amortizing the cost of
   I-cache loads across multiple packets.