From: Luis Chamberlain <mcgrof@kernel.org>
To: raymond.barbiero.dev@gmail.com
Cc: fstests@vger.kernel.org, jack@suse.cz,
mgorman@techsingularity.net, dave@stgolabs.net,
Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH 0/4] dbench: few enhancements from mmtests
Date: Wed, 9 Feb 2022 14:18:45 -0800 [thread overview]
Message-ID: <20220209221849.434616-1-mcgrof@kernel.org> (raw)
mmtests [0] also uses dbench, and they actually carry 4 patch delta
for years. These patches are useful and should not interfere
with existing uses, so just merge these.
As noted before, I've put all this and a few of my own fixes
into my own git tree [1] and I'll be extending dbench there as well
as I see its not up to date and even debian has dropped packaging
it as it doesn't compile anymore. The one on my tree compiles more
than fine now. I'll send a few other fixes after this set.
Mel, feel free to drop those patches if you want to use my tree :)
For lack of a mailing list for dbench, I'm freeloading off of fstests
as it uses dbench as well.
[0] https://github.com/gormanm/mmtests.git
[1] https://github.com/mcgrof/dbench.git
Jan Kara (1):
Allow reporting of workload execution times
Mel Gorman (3):
Defer reporting of execution times
libnfs: Include stdint.h
Check if parent is alive once per loadfile processed
child.c | 56 ++++++++++++++++++++++++++++++++++++++++++++++++++++----
dbench.c | 3 +++
dbench.h | 1 +
libnfs.c | 1 +
4 files changed, 57 insertions(+), 4 deletions(-)
--
2.34.1
next reply other threads:[~2022-02-09 22:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 22:18 Luis Chamberlain [this message]
2022-02-09 22:18 ` [PATCH 1/4] Allow reporting of workload execution times Luis Chamberlain
2022-02-09 22:18 ` [PATCH 2/4] Defer reporting of " Luis Chamberlain
2022-02-09 22:18 ` [PATCH 3/4] libnfs: Include stdint.h Luis Chamberlain
2022-02-09 22:18 ` [PATCH 4/4] Check if parent is alive once per loadfile processed Luis Chamberlain
2022-02-10 9:44 ` [PATCH 0/4] dbench: few enhancements from mmtests Jan Kara
2022-02-10 10:16 ` Mel Gorman
2022-02-10 13:04 ` Davidlohr Bueso
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=20220209221849.434616-1-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=dave@stgolabs.net \
--cc=fstests@vger.kernel.org \
--cc=jack@suse.cz \
--cc=mgorman@techsingularity.net \
--cc=raymond.barbiero.dev@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).