From: Peter Xu <peterx@redhat.com>
To: Daniel Wagner <dwagner@suse.de>
Cc: Clark Williams <williams@redhat.com>,
John Kacur <jkacur@redhat.com>,
linux-rt-users@vger.kernel.org
Subject: Re: [rt-tests v2 11/18] ptsematest: Streamline usage output and man page
Date: Wed, 10 Feb 2021 12:00:15 -0500 [thread overview]
Message-ID: <20210210170015.GL103365@xz-x1> (raw)
In-Reply-To: <20210210163537.t2tt3nyuqgkfzbl3@beryllium.lan>
On Wed, Feb 10, 2021 at 05:35:37PM +0100, Daniel Wagner wrote:
> --- a/src/oslat/oslat.c
> +++ b/src/oslat/oslat.c
> @@ -655,16 +655,10 @@ static void parse_options(int argc, char *argv[])
> */
> g.single_preheat_thread = true;
> break;
> - case 'v':
> - /*
> - * Because we always dump the version even before parsing options,
> - * what we need to do is to quit..
> - */
> - exit(0);
> - break;
> case 'z':
> g.output_omit_zero_buckets = 1;
> break;
> + case 'v':
> case 'h':
> usage(0);
> break;
>
>
>
> $ ./oslat -v
> oslat V 1.10
> Usage:
> oslat <options>
>
> This is an OS latency detector by running busy loops on specified cores.
> Please run this tool using root.
>
> Available options:
>
> -b, --bucket-size Specify the number of the buckets (4-1024)
> -B, --bias Add a bias to all the buckets using the estimated mininum
> -c, --cpu-list Specify CPUs to run on, e.g. '1,3,5,7-15'
> -C, --cpu-main-thread Specify which CPU the main thread runs on. Default is cpu0.
> -D, --duration Specify test duration, e.g., 60, 20m, 2H
> (m/M: minutes, h/H: hours, d/D: days)
> -f, --rtprio Using SCHED_FIFO priority (1-99)
> -m, --workload-mem Size of the memory to use for the workload (e.g., 4K, 1M).
> Total memory usage will be this value multiplies 2*N,
> because there will be src/dst buffers for each thread, and
> N is the number of processors for testing.
> -s, --single-preheat Use a single thread when measuring latency at preheat stage
> NOTE: please make sure the CPU frequency on all testing cores
> are locked before using this parmater. If you don't know how
> to lock the freq then please don't use this parameter.
> -T, --trace-threshold Stop the test when threshold triggered (in us),
> print a marker in ftrace and stop ftrace too.
> -v, --version Display the version of the software.
> -w, --workload Specify a kind of workload, default is no workload
> (options: no, memmove)
> -z, --zero-omit Don't display buckets in the output histogram if all zeros.
>
>
>
> The other tests print also the usage text which included the version if
> you provided '--version'. So this would make it behave in the same way.
> Good enough?
It makes sense to make all binaries in rt-tests behave similarly, so regarding
"oslat -v" even if it's not my preference, it's fine to me.
Again - Would you consider also dump the version in the output as before even
for a normal run?
--
Peter Xu
next prev parent reply other threads:[~2021-02-10 17:02 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 8:56 [rt-tests v2 00/18] Streamline command line Daniel Wagner
2020-10-07 8:56 ` [rt-tests v2 01/18] rt-util: Move parse_cpumask from cyclictest Daniel Wagner
2020-10-23 15:46 ` John Kacur
2020-10-26 18:34 ` Daniel Wagner
2020-10-29 15:45 ` John Kacur
2020-10-07 8:56 ` [rt-tests v2 02/18] cyclictest: Use numa library helpers in get_available_cpus() Daniel Wagner
2020-10-23 15:55 ` John Kacur
2020-10-07 8:56 ` [rt-tests v2 03/18] cyclicdeadline: Streamline usage output and man page Daniel Wagner
2020-10-23 16:01 ` John Kacur
2020-10-07 8:56 ` [rt-tests v2 04/18] cyclicdeadline: Add long command line options Daniel Wagner
2020-10-23 16:07 ` John Kacur
2020-10-27 8:07 ` Daniel Wagner
2020-10-07 8:56 ` [rt-tests v2 05/18] deadline_test: Streamline usage output and man page Daniel Wagner
2020-10-23 16:10 ` John Kacur
2020-10-07 8:56 ` [rt-tests v2 06/18] oslat: " Daniel Wagner
2020-10-23 17:19 ` John Kacur
2020-10-07 8:56 ` [rt-tests v2 07/18] oslat: Use string parser utilies Daniel Wagner
2020-10-23 17:25 ` John Kacur
2020-10-27 8:09 ` Daniel Wagner
2020-10-07 8:56 ` [rt-tests v2 08/18] pip_stress: Add command line parser Daniel Wagner
2020-10-23 17:33 ` John Kacur
2020-10-27 8:09 ` Daniel Wagner
2020-10-07 8:56 ` [rt-tests v2 09/18] pi_stress: Streamline usage output and man page Daniel Wagner
2020-10-07 8:56 ` [rt-tests v2 10/18] pmqtest: " Daniel Wagner
2020-10-23 18:18 ` John Kacur
2020-10-23 18:23 ` John Kacur
2020-10-07 8:56 ` [rt-tests v2 11/18] ptsematest: " Daniel Wagner
2020-10-23 18:25 ` John Kacur
2021-02-10 16:08 ` Peter Xu
2021-02-10 16:25 ` Peter Xu
2021-02-10 16:30 ` Daniel Wagner
2021-02-10 16:33 ` Peter Xu
2021-02-10 16:35 ` Daniel Wagner
2021-02-10 17:00 ` Peter Xu [this message]
2021-02-10 17:24 ` Daniel Wagner
2020-10-07 8:56 ` [rt-tests v2 12/18] queuelat: Streamline usage " Daniel Wagner
2020-10-23 18:40 ` John Kacur
2020-10-07 8:56 ` [rt-tests v2 13/18] rt-migrate-test: " Daniel Wagner
2020-10-23 18:47 ` John Kacur
2020-10-07 8:56 ` [rt-tests v2 14/18] signaltest: " Daniel Wagner
2020-10-23 18:50 ` John Kacur
2020-10-07 8:56 ` [rt-tests v2 15/18] sigwaittest: " Daniel Wagner
2020-10-23 18:51 ` John Kacur
2020-10-07 8:56 ` [rt-tests v2 16/18] ssdd: " Daniel Wagner
2020-10-23 18:57 ` John Kacur
2020-10-07 8:56 ` [rt-tests v2 17/18] svsematest: " Daniel Wagner
2020-10-23 18:59 ` John Kacur
2020-10-07 8:56 ` [rt-tests v2 18/18] hackbench: " Daniel Wagner
2020-10-23 19:03 ` John Kacur
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210210170015.GL103365@xz-x1 \
--to=peterx@redhat.com \
--cc=dwagner@suse.de \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).