On Fri, 4 Jul 2025, Ahmed S. Darwish wrote: > The number and breadth of cyclictest's options is huge, and just > exploring them in sequence can get the manpage reader lost. > > Put the cyclictest's memory-related option: > > -m, --mlockall > > into its own group. > > Further groupings will be added next. > > Signed-off-by: Ahmed S. Darwish <darwi@xxxxxxxxxxxxx> > --- > src/cyclictest/cyclictest.8 | 10 ++++++---- > 1 file changed, 6 insertions(+), 4 deletions(-) > > diff --git a/src/cyclictest/cyclictest.8 b/src/cyclictest/cyclictest.8 > index 7fc0420..a099416 100644 > --- a/src/cyclictest/cyclictest.8 > +++ b/src/cyclictest/cyclictest.8 > @@ -180,6 +180,12 @@ field in /proc/cpuinfo. See numa(3) for more information on specifying CPU > sets. * Support for CPU sets requires libnuma version >= 2. For libnuma > v1, PROC-SET, if specified, must be a single CPU number. > . > +.SS "Memory options" > +. > +.TP > +.B \-m, \-\-mlockall > +Lock current and future memory allocations to prevent being paged out > +. > .SS "Other options" > . > .TP > @@ -223,10 +229,6 @@ for automated tests with a given number of test cycles. Cyclictest is > stopped once the number of timer intervals has been reached. > . > .TP > -.B \-m, \-\-mlockall > -Lock current and future memory allocations to prevent being paged out > -. > -.TP > .B \\-M, \-\-refresh_on_max > Delay updating the screen until a new max latency is hit. (useful for > running cyclictest on low-bandwidth connections) > -- > 2.49.0 > > > Signed-off-by: John Kacur@xxxxxxxxxx>
