From: Vivek Goyal <vgoyal@redhat.com>
To: Jens Axboe <JAxboe@fusionio.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Have we changed number of fields in fio --minimal output
Date: Wed, 30 Jun 2010 07:37:55 -0600 [thread overview]
Message-ID: <20100630133755.GC6229@redhat.com> (raw)
In-Reply-To: <4C2B4565.1070402@fusionio.com>
On Wed, Jun 30, 2010 at 03:23:49PM +0200, Jens Axboe wrote:
[..]
> http://git.kernel.dk/?p=fio.git;a=commit;h=525c2bfabdb7e0093a8775a09ad3e772d962760e
>
> It's new prefixed with version 2, and I updated the documentation
> and man page as well on both the new format and the version field.
>
> Oh, and you were right about the 8 extra fields of course, it's 4
> added fields but it's per data direction.
Thanks. /me goes to update my scripts.
Vivek
prev parent reply other threads:[~2010-06-30 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 19:32 Have we changed number of fields in fio --minimal output Vivek Goyal
2010-06-30 7:31 ` Jens Axboe
2010-06-30 7:34 ` Jens Axboe
2010-06-30 7:44 ` Jens Axboe
2010-06-30 12:59 ` Vivek Goyal
2010-06-30 13:16 ` Jens Axboe
2010-06-30 13:23 ` Jens Axboe
2010-06-30 13:37 ` Vivek Goyal [this message]
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=20100630133755.GC6229@redhat.com \
--to=vgoyal@redhat.com \
--cc=JAxboe@fusionio.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