Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: fio@vger.kernel.org
Subject: Re: Measuring IOPS (solved, I think)
Date: Wed, 03 Aug 2011 09:17:05 +0200	[thread overview]
Message-ID: <4E38F5F1.6010502@kernel.dk> (raw)
In-Reply-To: <201108022328.52415.Martin@lichtvoll.de>

On 2011-08-02 23:28, Martin Steigerwald wrote:
> Am Dienstag, 2. August 2011 schrieben Sie:
>> That's a long email! The stonewall should be put in the job section
>> that has to wait for previous jobs. So, ala:
>>
>> [job1]
>> something
>>
>> [job2]
>> stonewall       # will wait for job1 to finish
>> something
>>
>> [job3]
>> something       # will run in parallel with job2
>>
>> [job4]
>> stonewall       # will run when job2+3 are finished
>> something
>>
>> If that's not the case, something is broken. A quick test here seems to
>> show that it works.
> 
> Its documented. From the manpage that I read several times by now:
> 
> Wait for preceding jobs in the job file to exit before starting this one.  
> stonewall implies new_group.
> 
> 
> Somehow despite my reading of manpage, README, HOWTO I came to the thought 
> that it tells fio to wait for the current job to finish, thus I had the 
> stonewall options misordered.
> 
> I expect that it works exactly as you said and try it this way. Instead of 
> omitting the last stonewall option in my iops job file I could omit the 
> first for the first job. Cause the first job does not need to wait for a 
> previous job.

Good, that makes me feel a little better :-)

Perhaps the name isn't that great? I'll gladly put in an alias for that
option, "wait_for_previous" or "barrier" or something like that. Fence?

-- 
Jens Axboe


  reply	other threads:[~2011-08-03  7:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-29 15:37 Measuring IOPS Martin Steigerwald
2011-07-29 16:14 ` Martin Steigerwald
2011-08-02 14:32   ` Measuring IOPS (solved, I think) Martin Steigerwald
2011-08-02 19:48     ` Jens Axboe
2011-08-02 21:28       ` Martin Steigerwald
2011-08-03  7:17         ` Jens Axboe [this message]
2011-08-03  9:03           ` Martin Steigerwald
2011-08-03 10:34             ` Jens Axboe
2011-08-03 19:31 ` Measuring IOPS Martin Steigerwald
2011-08-03 20:22   ` Jeff Moyer
2011-08-03 20:33     ` Martin Steigerwald
2011-08-04  7:50       ` Jens Axboe
2011-08-03 20:42     ` Martin Steigerwald
2011-08-03 20:50       ` Martin Steigerwald
2011-08-04  8:51         ` Martin Steigerwald
2011-08-04  8:58           ` Jens Axboe
2011-08-04  9:34             ` Martin Steigerwald
2011-08-04 10:02               ` Jens Axboe
2011-08-04 10:23                 ` Martin Steigerwald
2011-08-05  7:28                   ` 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=4E38F5F1.6010502@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=Martin@lichtvoll.de \
    --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