From: Shao-Tse Hung via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Cc: Shao-Tse Hung <ccs100203@gmail.com>
Subject: [lttng-dev] [PATCH] Fix: revise obsolete command in README.md
Date: Wed, 3 Aug 2022 01:44:00 +0800 [thread overview]
Message-ID: <20220802174400.219630-1-ccs100203@gmail.com> (raw)
The obsolete command `make bench` was replaced by `make short_bench` and `make long_bench` in 2015.
However, this command wasn't revised in README, so I follow the previous commit and rewrite it.
Signed-off-by: Shao-Tse Hung <ccs100203@gmail.com>
---
README.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index a8318c8..1e75589 100644
--- a/README.md
+++ b/README.md
@@ -426,14 +426,15 @@ Make targets
------------
In addition to the usual `make check` target, Userspace RCU features
-`make regtest` and `make bench` targets:
+`make regtest`, `make short_bench` and `make long_bench` targets:
- `make check`: short tests, meant to be run when rebuilding or
porting Userspace RCU.
- `make regtest`: long (many hours) test, meant to be run when
modifying Userspace RCU or porting it to a new architecture or
operating system.
- - `make bench`: long (many hours) benchmarks.
+ - `make short_bench`: short benchmarks, 3 seconds per test.
+ - `make long_bench`: long (many hours) benchmarks, 30 seconds per test.
Known issues
--
2.25.1
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next reply other threads:[~2022-08-02 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 17:44 Shao-Tse Hung via lttng-dev [this message]
2022-08-02 20:05 ` [lttng-dev] [PATCH] Fix: revise obsolete command in README.md Mathieu Desnoyers via lttng-dev
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=20220802174400.219630-1-ccs100203@gmail.com \
--to=lttng-dev@lists.lttng.org \
--cc=ccs100203@gmail.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).