From: Jens Axboe <axboe@kernel.dk>
To: Steven Lang <tirea@google.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: An alternative way to handle IO engine options
Date: Thu, 03 Nov 2011 12:38:23 +0100 [thread overview]
Message-ID: <4EB27D2F.1020502@kernel.dk> (raw)
In-Reply-To: <CAAUT-yNFcw6+8L911TYcSEED==QToxTbJLXZ8pA7Kuv6A=LqZw@mail.gmail.com>
On 2011-11-02 01:27, Steven Lang wrote:
> Alright I'll go ahead with finishing it.
>
> For the issue of global options... There are two possibilities I have
> in mind. The first is to limit it to just an ioengine that is
> specified, and the options for that ioengine are the only ioengine
> options that are allowed. That would probably be "good enough" for
> most cases. However, for a load which used two different IO engines,
> it would limit the global options to only one of the ioengines.
>
> The second option would be to have a way to specify options for
> different ioengines within the global section, then keep a copy of the
> config struct for each that is specified to use as a template.
>
> What I don't like about the second option is that the conf syntax for
> it might be somewhat messy.
>
> A third option would be to just parse the global options with respect
> to every known ioengine, or even just store the raw config values and
> parse them with each job.
>
> I'm not sure which is the best option; however unless there's some
> justification for doing otherwise I may just go with the first
> (simplest) for now, and if it becomes an issue the rest can be patched
> in later.
That sounds like a reasonable approach, we need not over-design it.
--
Jens Axboe
prev parent reply other threads:[~2011-11-03 11:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 20:16 An alternative way to handle IO engine options Steven Lang
2011-11-01 23:40 ` Jens Axboe
2011-11-02 0:27 ` Steven Lang
2011-11-03 11:38 ` 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=4EB27D2F.1020502@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=tirea@google.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