Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Reed Crowe <Reed.Crowe@sandisk.com>,
	"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: FIO creating empty latency log files
Date: Sat, 20 Jun 2015 13:22:49 -0400	[thread overview]
Message-ID: <5585A169.7090708@kernel.dk> (raw)
In-Reply-To: <5570BEAB.10707@sandisk.com>

On 06/04/2015 05:09 PM, Reed Crowe wrote:
>
> Using this version of FIO:
> * io-threads
>     master
> rcrowe@rcrowe-desktop:~/fio_iothreads/fio$ ./fio --version
> fio-2.2.7-14-g00b2
>
> I have a job file which looks like this:
>
> [global]
> ioengine=libaio
> direct=1
> numjobs=1
> bs=4k
> iodepth=300
> rw=randwrite
> randrepeat=0
> io_submit_mode=offload
> rate_iops=8070
> time_based=1
> runtime=1m
>
> [slow_write]
> filename=/mnt/test1/testfile.io
> write_lat_log=/tmp/fio_lat
>
> And it produces empty files:
> -rw-r--r-- 1 root   root         0 Jun  4 14:34 fio_lat_clat.1.log
> -rw-r--r-- 1 root   root         0 Jun  4 14:34 fio_lat_lat.1.log
> -rw-r--r-- 1 root   root         0 Jun  4 14:34 fio_lat_slat.1.log
>
> What am I missing?

Nothing, it was a bug in the io_submit_mode=offload code. Try updating 
to current -git, this should fix it:

http://git.kernel.dk/cgit/fio/commit/?id=75dc383e9d05369c830559496afa382178905e39

-- 
Jens Axboe



  reply	other threads:[~2015-06-20 17:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 21:09 FIO creating empty latency log files Reed Crowe
2015-06-20 17:22 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-10-27 15:41 Buttetsu Batou
2015-10-27 21:13 ` Jens Axboe
2015-10-28  0:20   ` Jens Axboe
2015-10-28  0:30     ` Jens Axboe
2015-10-28  2:19       ` DoubleDensity
2015-10-28  4:16         ` 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=5585A169.7090708@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=Reed.Crowe@sandisk.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