From: John Kacur <jkacur@redhat.com>
To: RT <linux-rt-users@vger.kernel.org>
Cc: Clark Williams <williams@redhat.com>,
Yunfeng Ye <yeyunfeng@huawei.com>, John Kacur <jkacur@redhat.com>
Subject: [PATCH] rt-tests: hachbench: Update the usage and man page for -F|--fifo option
Date: Tue, 5 May 2020 12:40:01 -0400 [thread overview]
Message-ID: <20200505164001.5705-1-jkacur@redhat.com> (raw)
From: Yunfeng Ye <yeyunfeng@huawei.com>
The commit 6c0c79b5152a ("hackbench mods to work better under stress")
add -F|--fifo option, but not update the usage and man page, so this
patch fix it.
Signed-off-by: Yunfeng Ye <yeyunfeng@huawei.com>
Signed-off-by: John Kacur <jkacur@redhat.com>
- Fixed-up rejected patch hunk in man page
- Changed the wording in the man page
---
src/hackbench/hackbench.8 | 6 +++++-
src/hackbench/hackbench.c | 2 +-
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/src/hackbench/hackbench.8 b/src/hackbench/hackbench.8
index d86c52f27a2e..aaf572359704 100644
--- a/src/hackbench/hackbench.8
+++ b/src/hackbench/hackbench.8
@@ -7,7 +7,7 @@ hackbench \- scheduler benchmark/stress test
.RI "[\-l|\-\-loops " <num\-loops> "] "
.RI "[\-g|\-\-groups "<num\-groups> "] "
.RI "[\-f|\-\-fds <num\-fds>] "
-.RI "[\-T|\-\-threads] [\-P|\-\-process] [\-\-help]"
+.RI "[\-T|\-\-threads] [\-P|\-\-process] [\-F|\-\-fifo] [\-\-help]"
.SH "DESCRIPTION"
Hackbench is both a benchmark and a stress test for the Linux kernel
@@ -45,6 +45,10 @@ Each sender/receiver child will be a POSIX thread of the parent.
.TP
.B \-P, \-\-process
Hackbench will use fork() on all children (default behaviour)
+.TP
+.B \-F,\-\-fifo
+Change the main thread to SCHED_FIFO after creating workers.
+This allows the management thread to run after many workers are created.
.TP
.B \-\-help
.br
diff --git a/src/hackbench/hackbench.c b/src/hackbench/hackbench.c
index 5a883d341f2e..2cddff654df6 100644
--- a/src/hackbench/hackbench.c
+++ b/src/hackbench/hackbench.c
@@ -92,7 +92,7 @@ static void print_usage_exit()
{
printf("Usage: hackbench [-p|--pipe] [-s|--datasize <bytes>] [-l|--loops <num loops>]\n"
"\t\t [-g|--groups <num groups] [-f|--fds <num fds>]\n"
- "\t\t [-T|--threads] [-P|--process] [--help]\n");
+ "\t\t [-T|--threads] [-P|--process] [-F|--fifo] [--help]\n");
exit(1);
}
--
2.21.3
next reply other threads:[~2020-05-05 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 16:40 John Kacur [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-28 7:11 [PATCH] rt-tests: hachbench: Update the usage and man page for -F|--fifo option Yunfeng Ye
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=20200505164001.5705-1-jkacur@redhat.com \
--to=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.com \
--cc=yeyunfeng@huawei.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).