C-Docs: New structure

[csit.git] / docs / content / methodology / overview / multi_core_speedup.md

diff --git a/docs/content/methodology/multi_core_speedup.md b/docs/content/methodology/overview/multi_core_speedup.md
similarity index 86%
rename from docs/content/methodology/multi_core_speedup.md
rename to docs/content/methodology/overview/multi_core_speedup.md
index c0c9ae2..f438e8e 100644 (file)
--- a/docs/content/methodology/multi_core_speedup.md
+++ b/docs/content/methodology/overview/multi_core_speedup.md
@@ -1,6 +1,6 @@
 ---
 title: "Multi-Core Speedup"
-weight: 13
+weight: 3
 ---
 
 # Multi-Core Speedup
@@ -25,12 +25,12 @@ Cascadelake and Xeon Icelake testbeds.
 Multi-core tests are executed in the following VPP worker thread and physical
 core configurations:
 
-#. Intel Xeon Icelake and Cascadelake testbeds (2n-icx, 3n-icx, 2n-clx)
+1. Intel Xeon Icelake and Cascadelake testbeds (2n-icx, 3n-icx, 2n-clx)
    with Intel HT enabled (2 logical CPU cores per each physical core):
 
-  #. 2t1c - 2 VPP worker threads on 1 physical core.
-  #. 4t2c - 4 VPP worker threads on 2 physical cores.
-  #. 8t4c - 8 VPP worker threads on 4 physical cores.
+   1. 2t1c - 2 VPP worker threads on 1 physical core.
+   2. 4t2c - 4 VPP worker threads on 2 physical cores.
+  3. 8t4c - 8 VPP worker threads on 4 physical cores.
 
 VPP worker threads are the data plane threads running on isolated
 logical cores. With Intel HT enabled VPP workers are placed as sibling
@@ -48,4 +48,4 @@ the same amount of packet flows.
 If number of VPP workers is higher than number of physical or virtual
 interfaces, multiple receive queues are configured on each interface.
 NIC Receive Side Scaling (RSS) for physical interfaces and multi-queue
-for virtual interfaces are used for this purpose.
\ No newline at end of file
+for virtual interfaces are used for this purpose.