Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Matthew Eaton <m.eaton82@gmail.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Fio 2.1.14 released
Date: Tue, 11 Nov 2014 18:24:00 -0700	[thread overview]
Message-ID: <5462B6B0.3010003@kernel.dk> (raw)
In-Reply-To: <CAF+0mv=H9cauEbP+CMCup0aLUD0qE42Jz9WPzboAv0U757acYw@mail.gmail.com>

On 2014-11-11 18:11, Matthew Eaton wrote:
>> - Fio will exit a bit faster now, since the disk util thread and the
>>    helper thread were combined into one, and it'll be immediately torn
>>    down on exit. It had to wait around 250msecs before this change. You
>>    might have noticed this delay when doing ctrl-c on a workload.
>
> I find this update interesting, as I have a script that calls fio
> multiple times, one after the other.
>
> Are there any options that would make fio start or exit faster?  For
> example, if I used disk_util=0, would this help fio exit any faster?

It should all be as fast as it could be before. The issue fixed above is 
when we wanted the disk util thread to exit, we set a done flag and just 
waited for it to wakeup as, which it did a few times per second. Now we 
use regular condvars, so it'll wake and exit immediately. So disk_util=0 
should not change more than a msec or so :-)

That said, if you do find things where it seems to start or stop slower 
than it should, let me know. But as far as I know, it's all properly 
driven now.

-- 
Jens Axboe



  reply	other threads:[~2014-11-12  1:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11 21:14 Fio 2.1.14 released Jens Axboe
2014-11-11 21:52 ` Stephen Cameron
2014-11-11 21:54   ` Jens Axboe
2014-11-12  1:11 ` Matthew Eaton
2014-11-12  1:24   ` Jens Axboe [this message]
2014-11-12 21:36     ` Matthew Eaton
2014-11-12 21:37       ` 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=5462B6B0.3010003@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=m.eaton82@gmail.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