C-Docs: New structure

[csit.git] / docs / content / methodology / per_patch_testing.md

diff --git a/docs/content/methodology/root_cause_analysis/perpatch_performance_tests.md b/docs/content/methodology/per_patch_testing.md
similarity index 95%
rename from docs/content/methodology/root_cause_analysis/perpatch_performance_tests.md
rename to docs/content/methodology/per_patch_testing.md
index 900ea0b..a64a52c 100644 (file)
--- a/docs/content/methodology/root_cause_analysis/perpatch_performance_tests.md
+++ b/docs/content/methodology/per_patch_testing.md
@@ -1,9 +1,9 @@
 ---
-title: "Per-patch performance tests"
-weight: 1
+title: "Per-patch Testing"
+weight: 5
 ---
 
-# Per-patch performance tests
+# Per-patch Testing
 
 Updated for CSIT git commit id: 72b45cfe662107c8e1bb549df71ba51352a898ee.
 
@@ -101,15 +101,15 @@ where the variables are all lower case (so AND operator stands out).
 
 Currently only one test type is supported by the performance comparison jobs:
 "mrr".
-The nic_driver options depend on nic_model. For Intel cards "drv_avf" (AVF plugin)
-and "drv_vfio_pci" (DPDK plugin) are popular, for Mellanox "drv_rdma_core".
-Currently, the performance using "drv_af_xdp" is not reliable enough, so do not use it
-unless you are specifically testing for AF_XDP.
+The nic_driver options depend on nic_model. For Intel cards "drv_avf"
+(AVF plugin) and "drv_vfio_pci" (DPDK plugin) are popular, for Mellanox
+"drv_rdma_core". Currently, the performance using "drv_af_xdp" is not reliable
+enough, so do not use it unless you are specifically testing for AF_XDP.
 
 The most popular nic_model is "nic_intel-xxv710", but that is not available
 on all testbed types.
-It is safe to use "1c" for cores (unless you are suspection multi-core performance
-is affected differently) and "64b" for frame size ("78b" for ip6
+It is safe to use "1c" for cores (unless you are suspection multi-core
+performance is affected differently) and "64b" for frame size ("78b" for ip6
 and more for dot1q and other encapsulated traffic;
 "1518b" is popular for ipsec and other payload-bound tests).
 
@@ -121,9 +121,11 @@ for example
 
 ### Shortening triggers
 
-Advanced users may use the following tricks to avoid writing long trigger comments.
+Advanced users may use the following tricks to avoid writing long trigger
+comments.
 
-Robot supports glob matching, which can be used to select multiple suite tags at once.
+Robot supports glob matching, which can be used to select multiple suite tags at
+once.
 
 Not specifying one of 6 parts of the recommended expression pattern
 will select all available options. For example not specifying nic_driver