From: Erwan Velu <erwan@enovance.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: How to loop a timebased job
Date: Wed, 04 Sep 2013 22:02:28 +0200 [thread overview]
Message-ID: <522791D4.3060201@enovance.com> (raw)
In-Reply-To: <52277371.5070004@kernel.dk>
On 04/09/2013 19:52, Jens Axboe wrote:
> Good point, yes, that is a problem. Adding a loopbased option would
> seem to be the best way to solve the dependency issue.
Ok, I'm working on this option.
Here come the kind of usage I'm thinking about :
[general]
....
loop_based
loops=5
[job_1]
....
runtime=10
[job_2]
....
runtime=20
That lever the question on where we shall "loop" the jobs ?
What's the preferred option regarding your experience on fio ?
The main problem I'm facing is to reinit properly jobs between loops
(like td->terminate or doing the start_delay,...)
Shall it be better to manage it inside thread_main() or get it outside ?
Thanks for your insights,
Erwan
next prev parent reply other threads:[~2013-09-04 20:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 19:34 How to loop a timebased job Erwan Velu
2013-09-03 22:37 ` Jens Axboe
2013-09-04 13:56 ` Erwan Velu
2013-09-04 17:52 ` Jens Axboe
2013-09-04 20:02 ` Erwan Velu [this message]
2013-09-04 20:11 ` 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=522791D4.3060201@enovance.com \
--to=erwan@enovance.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.