From: Daniel Wagner <dwagner@suse.de>
To: Clark Williams <williams@redhat.com>, John Kacur <jkacur@redhat.com>
Cc: linux-rt-users@vger.kernel.org, Daniel Wagner <dwagner@suse.de>
Subject: [rt-tests v2 00/18] Streamline command line
Date: Wed, 7 Oct 2020 10:56:35 +0200 [thread overview]
Message-ID: <20201007085653.11961-1-dwagner@suse.de> (raw)
Hi,
Here the second round getting the some more consistency into the code
base. With this all the commands should at least look the same and use
an consistent option name. I've tried to make it backwards compatible,
except for oslat (--duration).
Thanks,
Daniel
changes since v1:
- updated all existing tools
Daniel Wagner (18):
rt-util: Move parse_cpumask from cyclictest
cyclictest: Use numa library helpers in get_available_cpus()
cyclicdeadline: Streamline usage output and man page
cyclicdeadline: Add long command line options
deadline_test: Streamline usage output and man page
oslat: Streamline usage output and man page
oslat: Use string parser utilies
pip_stress: Add command line parser
pi_stress: Streamline usage output and man page
pmqtest: Streamline usage output and man page
ptsematest: Streamline usage output and man page
queuelat: Streamline usage and man page
rt-migrate-test: Streamline usage and man page
signaltest: Streamline usage and man page
sigwaittest: Streamline usage and man page
ssdd: Streamline usage and man page
svsematest: Streamline usage and man page
hackbench: Streamline usage and man page
Makefile | 12 +--
src/cyclictest/cyclictest.c | 90 +++-------------
src/hackbench/hackbench.8 | 70 +++++++------
src/hackbench/hackbench.c | 102 +++++++++---------
src/include/rt-utils.h | 3 +
src/lib/rt-utils.c | 76 ++++++++++++++
src/oslat/oslat.8 | 2 +-
src/oslat/oslat.c | 145 +++++++-------------------
src/pi_tests/pi_stress.8 | 79 +++++++-------
src/pi_tests/pi_stress.c | 144 +++++++++++++------------
src/pi_tests/pip_stress.c | 34 +++++-
src/pmqtest/pmqtest.8 | 5 +-
src/pmqtest/pmqtest.c | 88 ++++++++--------
src/ptsematest/ptsematest.8 | 5 +-
src/ptsematest/ptsematest.c | 76 +++++++-------
src/queuelat/queuelat.8 | 41 +++-----
src/queuelat/queuelat.c | 99 +++++++++---------
src/rt-migrate-test/rt-migrate-test.8 | 41 ++++----
src/rt-migrate-test/rt-migrate-test.c | 82 +++++++--------
src/sched_deadline/cyclicdeadline.8 | 25 ++---
src/sched_deadline/cyclicdeadline.c | 67 +++++++-----
src/sched_deadline/deadline_test.8 | 37 ++++---
src/sched_deadline/deadline_test.c | 47 ++++-----
src/signaltest/signaltest.8 | 13 +--
src/signaltest/signaltest.c | 47 +++++----
src/sigwaittest/sigwaittest.8 | 4 +-
src/sigwaittest/sigwaittest.c | 76 ++++++++------
src/ssdd/ssdd.8 | 35 +++----
src/ssdd/ssdd.c | 50 +++++----
src/svsematest/svsematest.8 | 6 +-
src/svsematest/svsematest.c | 83 ++++++++-------
31 files changed, 854 insertions(+), 830 deletions(-)
--
2.28.0
next reply other threads:[~2020-10-07 8:56 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 8:56 Daniel Wagner [this message]
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
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=20201007085653.11961-1-dwagner@suse.de \
--to=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).