Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: thoms@voicenet.com, Carl Zwanzig <cpz@coraid.com>,
	"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Stonewalled ?
Date: Thu, 26 Feb 2015 13:50:09 -0700	[thread overview]
Message-ID: <54EF8701.9020008@kernel.dk> (raw)
In-Reply-To: <54EF31C0.9030502@voicenet.com>

On 02/26/2015 07:46 AM, thoms wrote:
> 
> On 02/26/2015 02:11 AM, Carl Zwanzig wrote:
>> (sorry about top-posting here)
>>
>> For things like this, I'd use an external script specifying all params on each command line, and not use a job file at all. Order of execution is guaranteed and there's no limit to the number of jobs. (When fio evaluates the job file it creates all the jobs, but then doesn't let them all start at once.)
>>
>> z!
>> ________
> 
> I'm prepared to do that, it's just messy for my particular situation. 
> Not having looked through the code, I was under the impression that
> "stonewall" changed the semantics of that behavior.  Understood...
> 
> Thanks for the insight.  Much appreciated...

The stonewall does do what you expect. The problem isn't related to how
many jobs are running at the same time, it's how many jobs have been
added. Basically it boils down to how big of an shm segment fio will
need to run.

You could always just bump REAL_MAX_JOBS in fio.h to something larger
than 2048, that should work on most platforms.

-- 
Jens Axboe



      reply	other threads:[~2015-02-26 20:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26  4:04 Stonewalled ? thoms
2015-02-26  7:11 ` Carl Zwanzig
2015-02-26 14:46   ` thoms
2015-02-26 20:50     ` Jens Axboe [this message]

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=54EF8701.9020008@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=cpz@coraid.com \
    --cc=fio@vger.kernel.org \
    --cc=thoms@voicenet.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