Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Status
Date: Thu, 12 Apr 2012 09:28:46 +0200	[thread overview]
Message-ID: <4F86842E.4040201@kernel.dk> (raw)

Hi,

In case you didn't notice, fio-2.0.7 was tagged yesterday. After
tagging 2.0.7, I pulled in a few changes from the gfio branch
that you might like to know about.

One is the ability to dump the normal end output while fio keeps
running. This is useful for long running jobs, where you might
like to know what's going on outside of just the IOPS and throughput
numbers etc. If you send the master fio process a USR1 signal,
it'll display the normal end of job output now and continue doing
it's thing. It's done outside of the normal IO paths and by a
separate thread off the signal, so impact on the actual job should
be minimal.

Another change is the inclusion of parts of the git sha in the
fio version output. It used to just be fio-2.0.6 for any version
between 2.0.6 and 2.0.7, but now it also includes the current
git sha:

axboe@nelson:/home/axboe/git/fio $ ./fio --version
fio-2.0.7-5-g8423b

Since some people have scripts that parse the output, I thought
I'd mention it here as well.

Outside of the master branch, gfio has made some progress. It's now
good enough to run existing jobs, either locally or on a remote
machine. There's still a bunch of things missing, like a better
results manager, ability to print output, and actual working support
for editing a job either from scratch or from an existing job file.
If you are interested in this gtk2/3 frontend for fio, I'd
encourage you to give it a shot. It's mostly for developers at this
point, but any sort of input would be useful.

-- 
Jens Axboe


             reply	other threads:[~2012-04-12  7:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12  7:28 Jens Axboe [this message]
2012-04-12 15:16 ` Status Martin Steigerwald
2012-04-12 17:32   ` Status 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=4F86842E.4040201@kernel.dk \
    --to=axboe@kernel.dk \
    --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