Flexible I/O Tester development
 help / color / mirror / Atom feed
From: ehrhardt@linux.vnet.ibm.com
To: fio@vger.kernel.org
Cc: oberpar@linux.vnet.ibm.com
Subject: [patch 0/9] Collection of various fio fixes and extensions V2
Date: Thu, 20 Feb 2014 14:19:58 +0100	[thread overview]
Message-ID: <20140220131958.965092001@linux.vnet.ibm.com> (raw)

*Resend with hopefully non mangled patches*

Hi,
we adopted fio as a very good tool back at version 1.57.
It suited our needs in replacing iozone with a more modern and more capable
benchmarking tool.

As it is usually we needed a few little extensions to support the old use
cases we wanted to migrate to the new benchmark. Also we found a few issues
in the fio code that we had to fix.

All that happened a long time back and we always wanted to cotribute our
changes to the project which after a loooong legal process now is finally
possible. To make things worse the code was affected by some bit rot due
to that legal waiting time which in turn stalled me making it ready for
submission again.

I'm happy that I finally found some time to update the patches to match to
the current fio git. It passed my 18 test cases which are based on the
examples delivered with fio new for the new functionality added.

Looking forward to your review,
Christian

The patch series includes:
[patch 1/9] fio: fix job clone mem leak
[patch 2/9] fio: allow general repeatability
[patch 3/9] fio: allow milliseconds on all time specifiers
[patch 4/9] fio: provide an option for a startdelay range
[patch 5/9] fio: add multi directory support
[patch 6/9] fio: allow combined output (default and terse)
[patch 7/9] fio: flush log files on test end
[patch 8/9] fio: fix last block never being touched by random offsets
[patch 9/9] fio: allow 0 as compress percentage

 backend.c     |    5 +--
 engines/net.c |    2 -
 eta.c         |   14 +++++----
 file.h        |    8 ++++-
 filesetup.c   |   70 +++++++++++++++++++++++++++++++++++++++++-----
 fio.1         |   48 +++++++++++++++++++++++--------
 fio.h         |    6 +++
 init.c        |   64 +++++++++++++++++++++++++++++++++++++-----
 io_u.c        |    2 -
 iolog.c       |    2 -
 iolog.h       |    1 
 options.c     |   88 ++++++++++++++++++++++++++++++++++++++++++++++------------
 options.h     |    2 +
 parse.c       |   48 ++++++++++++++++++++++---------
 stat.c        |   83 ++++++++++++++++++++++++++++++++++++++----------------
 time.c        |    2 -
 16 files changed, 349 insertions(+), 96 deletions(-)


             reply	other threads:[~2014-02-20 13:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 13:19 ehrhardt [this message]
2014-02-20 17:20 ` [patch 0/9] Collection of various fio fixes and extensions V2 Jens Axboe
2014-02-21  9:03   ` Christian Ehrhardt

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=20140220131958.965092001@linux.vnet.ibm.com \
    --to=ehrhardt@linux.vnet.ibm.com \
    --cc=fio@vger.kernel.org \
    --cc=oberpar@linux.vnet.ibm.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