From: John Kacur <jkacur@redhat.com>
To: rt-users <linux-rt-users@vger.kernel.org>
Cc: Clark Williams <williams@redhat.com>, John Kacur <jkacur@redhat.com>
Subject: [PATCH 7/8] svsematest: Add -S, --smp option to manpage
Date: Mon, 25 Nov 2019 15:16:43 +0100 [thread overview]
Message-ID: <20191125141644.4429-5-jkacur@redhat.com> (raw)
In-Reply-To: <20191125141644.4429-1-jkacur@redhat.com>
The -S, or --smp option is in the help but missing from the manpage.
We should really revisit these tests as these options have changed a bit
in cyclictest and they are all modeled after cyclictest.
Signed-off-by: John Kacur <jkacur@redhat.com>
---
src/svsematest/svsematest.8 | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/svsematest/svsematest.8 b/src/svsematest/svsematest.8
index f67ab4c669d3..98322c105803 100644
--- a/src/svsematest/svsematest.8
+++ b/src/svsematest/svsematest.8
@@ -38,6 +38,9 @@ Set the number of loops. The default is 0 (endless). This option is useful for a
.B \-p, \-\-prio=PRIO
Set the priority of the process.
.TP
+.B \-S, \-\-smp
+SMP testing: options -a -t and same priority of all threads
+.TP
.B \-t, \-\-threads[=NUM]
Set the number of test threads (default is 1, if this option is not given). If NUM is specified, create NUM test threads. If NUM is not specified, NUM is set to the number of available CPUs.
.SH "EXAMPLES"
--
2.20.1
next prev parent reply other threads:[~2019-11-25 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 14:16 [PATCH 1/8] rt-tests: queuelat: Fix some warnings in determine_maximum_mpps.sh John Kacur
2019-11-25 14:16 ` [PATCH 2/8] rt-tests: ssdd: Add short and long functions as well as help John Kacur
2019-11-25 14:16 ` [PATCH 5/8] rt-tests: cyclictest: Get a snapshot of cyclictest without interuppting it John Kacur
2019-11-25 14:16 ` [PATCH 6/8] cyclictest: Sync manpage with the help option John Kacur
2019-11-25 14:16 ` John Kacur [this message]
2019-11-25 14:16 ` [PATCH 8/8] rt-tests: Add SPDX tags John Kacur
2019-11-25 14:33 ` Sebastian Andrzej Siewior
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=20191125141644.4429-5-jkacur@redhat.com \
--to=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).