From: Jens Axboe <axboe@kernel.dk>
To: Carl Zwanzig <cpz@coraid.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: use of rwmixread option
Date: Fri, 1 Feb 2013 01:00:55 +0100 [thread overview]
Message-ID: <20130201000055.GG25524@kernel.dk> (raw)
In-Reply-To: <A7A1D348E34E024BBC74480FB93A2EAB010719@DAGN05A-E6.exg6.exghost.com>
On Thu, Jan 31 2013, Carl Zwanzig wrote:
> Hi,
>
> Am I correct that rwmixread/rwmixwrite are completely ignored unless
> readwrite=rw or =randrw? Experiments suggest yes but I can't find
> where this is handled in the code. (The HowTo file is silent on this.)
That is correct, see io_u.c:get_rw_ddir(). The mix is only used if the
data direciton is read-write. For pure read, always reads, for pure
writes, always writes.
> *Is there a description somewhere on how options are processed?
> Tracking the option definition in options.c to its use has eluded me.
So the options.c bits only ensure that the options are set. That is
td->o.rwmix[]. The options ensure that mixread + mixwrite == 100%. The
actual handling is in the function mentioned above, plus it interacts
with an IO issue counter. Essentially the mix is IOPS based, with
randomness for direction chosen.
--
Jens Axboe
prev parent reply other threads:[~2013-02-01 0:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 23:43 use of rwmixread option Carl Zwanzig
2013-02-01 0:00 ` 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=20130201000055.GG25524@kernel.dk \
--to=axboe@kernel.dk \
--cc=cpz@coraid.com \
--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