Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: ehrhardt@linux.vnet.ibm.com
Cc: fio@vger.kernel.org, oberpar@linux.vnet.ibm.com
Subject: Re: [patch 0/9] Collection of various fio fixes and extensions V2
Date: Thu, 20 Feb 2014 09:20:33 -0800	[thread overview]
Message-ID: <20140220172033.GD30251@kernel.dk> (raw)
In-Reply-To: <20140220131958.965092001@linux.vnet.ibm.com>

On Thu, Feb 20 2014, ehrhardt@linux.vnet.ibm.com wrote:
> *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.

Glad to hear it!

> 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.

I have applied all of the patches directly, except for 8/9. I fixed up
the options issues I noted, and also fixed up rbd not being updated for
the multidirectory support.

Thanks!

-- 
Jens Axboe



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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 13:19 [patch 0/9] Collection of various fio fixes and extensions V2 ehrhardt
2014-02-20 17:20 ` Jens Axboe [this message]
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=20140220172033.GD30251@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=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