Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Mike Ryan <mike.ryan@inktank.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: fio@vger.kernel.org
Subject: Re: generating latency logs
Date: Tue, 7 Aug 2012 07:47:21 -0700	[thread overview]
Message-ID: <20120807144721.GF12248@splice> (raw)
In-Reply-To: <50211B6A.2070505@kernel.dk>

On Tue, Aug 07, 2012 at 03:43:06PM +0200, Jens Axboe wrote:
> >   fio --latency-log=/tmp/log --output=/tmp/log random_write.fio
> 
> The latency/bw logs are named from the job name, so you can't actually
> give it a specific name with the (global) command line option. You'd
> need to use the job option to do that.

The argument requires an option. It appears that option is discarded.

> That said, it does look broken in that we don't inherit the global
> setting. Does the below make it work?

Yes! The files are named log_lat.log, log_slat.log, and log_clat.log.
They are not named after the job.


  reply	other threads:[~2012-08-07 14:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07  1:03 generating latency logs Mike Ryan
2012-08-07 13:43 ` Jens Axboe
2012-08-07 14:47   ` Mike Ryan [this message]
2012-08-08  5:23     ` Kyle Hailey
2012-08-08  5:26     ` Kyle Hailey

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=20120807144721.GF12248@splice \
    --to=mike.ryan@inktank.com \
    --cc=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