diff options
| author |   Vratko Polak <vrpolak@cisco.com> | 2022-10-17 15:08:16 +0200 |
|---|---|---|
| committer |   Tibor Frank <tifrank@cisco.com> | 2022-10-18 08:13:26 +0000 |
| commit | 6809aeefd0f2b951cd4861f676ee2dff0df47ff2 (patch) | |
| tree | c0edacd0afcb31262f99701e67f0a600a4e07da1 /docs/report/introduction/methodology_dut_state.rst | |
| parent | 4b246a2bf50fd42ec3343dc317e7828d8b0d82da (diff) | |
fix(report): unify .rst section marks
Unify characters marking section levels,
(at least for methodology Vratko contributed to):
Level 0: ==== Do not use, or use for index.rst only.
(Because git conflicts also create ====.)
Level 1: ^^^^
Level 2: ~~~~
Level 3: ````
Level 4: ____
Level 5: ---- Do not use.
(Because other documents use this as level 0,
and it also appears in tables.)
Change-Id: I10813f718b2ee34d1e34c58e62e88353000340e9
Signed-off-by: Vratko Polak <vrpolak@cisco.com>
Diffstat (limited to 'docs/report/introduction/methodology_dut_state.rst')
| -rw-r--r-- | docs/report/introduction/methodology_dut_state.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/report/introduction/methodology_dut_state.rst b/docs/report/introduction/methodology_dut_state.rst index d08e42513d..3792e31ecf 100644 --- a/docs/report/introduction/methodology_dut_state.rst +++ b/docs/report/introduction/methodology_dut_state.rst @@ -1,5 +1,5 @@ DUT state considerations ------------------------- +^^^^^^^^^^^^^^^^^^^^^^^^ This page discusses considerations for Device Under Test (DUT) state. DUTs such as VPP require configuration, to be provided before the aplication @@ -42,7 +42,7 @@ As the performance is different, each test has to choose which traffic it wants to test, and manipulate the DUT state to achieve the intended impact. Ramp-up trial -_____________ +````````````` Tests aiming at sustain performance need to make sure DUT state is created. We achieve this via a ramp-up trial, specific purpose of which @@ -67,7 +67,7 @@ it has been created as expected. Test fails if the state is not (completely) created. State Reset -___________ +``````````` Tests aiming at ramp-up performance do not use ramp-up trial, and they need to reset the DUT state before each trial measurement. @@ -94,7 +94,7 @@ If neither were used, DUT will show different performance in subsequent trials, violating assumptions of search algorithms. DUT versus protocol ramp-up -___________________________ +``````````````````````````` There are at least three different causes for bandwidth possibly increasing within a single measurement trial. |