From: Jens Axboe <axboe@kernel.dk>
To: "Jeffrey McVay (jmcvay)" <jmcvay@micron.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: FIO 2.1 iops logging problem
Date: Wed, 29 May 2013 10:46:23 +0200 [thread overview]
Message-ID: <20130529084623.GO22724@kernel.dk> (raw)
In-Reply-To: <C8CA972100601A41AE302914E9CE194680367B7E@NTXBOIMBX03.micron.com>
On Tue, May 28 2013, Jeffrey McVay (jmcvay) wrote:
> Hi Jens,
>
> I cannot seem to get the write_iops_log working with FIO 2.1.
>
> I found that write_bw_log now requires write_bw_log=<text> to work.
> However that does not seem to work on the iops logging. Any idea what
> I am doing wrong?
Looks like a merge error between fio and gfio, I have fixed it up now. I
will be doing a 2.1.1 shortly, since it's not the only one that has
cropped up.
This is the patch:
http://git.kernel.dk/?p=fio.git;a=commit;h=577c83bd488cf3e92d4ccffd39659248bce8ccd3
It has been committed.
--
Jens Axboe
next prev parent reply other threads:[~2013-05-29 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 21:01 FIO 2.1 iops logging problem Jeffrey McVay (jmcvay)
2013-05-29 8:46 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-28 21:17 Jeffrey McVay (jmcvay)
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=20130529084623.GO22724@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=jmcvay@micron.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