Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "Justin Eno (jeno)" <jeno@micron.com>,
	"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: [RFC] [PATCH] Allow random overwrite workloads to write io_limit
Date: Mon, 16 Feb 2015 15:00:56 -0700	[thread overview]
Message-ID: <54E26898.5030706@kernel.dk> (raw)
In-Reply-To: <5A8251503902B84E89CE171AD126BCFB2DE5C431@NTXBOIMBX01.micron.com>

On 02/13/2015 04:17 PM, Justin Eno (jeno) wrote:
> For a (random) overwrite workload, 'size' amount of access doesn't correspond to
> each byte on the target having been touched, so setting size as the limit between
> write- and verify-phases doesn't really apply.  The attached patch proposes to
> instead use io_limit as the limit if it's set.
>
> io_limit < size is already handled by subsequent logic.  This patch just allows
> for io_limit > size.

Thanks Justin, applied.

-- 
Jens Axboe



      reply	other threads:[~2015-02-16 22:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13 23:17 [RFC] [PATCH] Allow random overwrite workloads to write io_limit Justin Eno (jeno)
2015-02-16 22: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=54E26898.5030706@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=jeno@micron.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