From: Andreas Herrmann <aherrmann@suse.com>
To: Jens Axboe <axboe@fb.com>
Cc: fio@vger.kernel.org
Subject: [PATCH v4 0/4] stat: Modify info for bw and add iops stats
Date: Sat, 24 Jun 2017 00:27:34 +0200 [thread overview]
Message-ID: <20170623222738.5146-1-aherrmann@suse.com> (raw)
Hi,
Next try. Changes to previous version:
[PATCH 1/4] stat: Print one-line iops stat
- Added client conversion and bump server version
[PATCH 2/4] stat: Print number of samples in bw and iops stats
[PATCH 3/4] stat: Merge show_thread_status_terse_* functions
[PATCH 4/4] stat: Add iops stat and sample number information to
- Added explanation of v5 terse format to man page and HOWTO
- Continue to report TRIM status with terse version 5
One oddity I've spotted is that man page states
"text description (if provided in config - appears on newline)"
But I think that this applies only to v2 terse format.
My merge of the terse output functions tried to preserve the code as
is so no newline for v3 and above.
If the newline is the desired behaviour I'll send a follow-on patch to
adapt the code to the man-page (and if not vice versa).
Regards,
Andreas
next reply other threads:[~2017-06-23 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 22:27 Andreas Herrmann [this message]
2017-06-23 22:27 ` [PATCH 1/4] stat: Print one-line iops stat Andreas Herrmann
2017-06-26 14:30 ` Elliott, Robert (Persistent Memory)
2017-06-26 14:52 ` Jens Axboe
2017-06-23 22:27 ` [PATCH 2/4] stat: Print number of samples in bw and iops stats Andreas Herrmann
2017-06-23 22:27 ` [PATCH 3/4] stat: Merge show_thread_status_terse_* functions Andreas Herrmann
2017-06-23 22:27 ` [PATCH 4/4] stat: Add iops stat and sample number information to terse format Andreas Herrmann
2017-06-23 22:31 ` [PATCH v4 0/4] stat: Modify info for bw and add iops stats Jens Axboe
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=20170623222738.5146-1-aherrmann@suse.com \
--to=aherrmann@suse.com \
--cc=axboe@fb.com \
--cc=fio@vger.kernel.org \
/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