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 verification of random overwrites w/ba < bs
Date: Wed, 18 Feb 2015 10:38:15 -0800	[thread overview]
Message-ID: <54E4DC17.1080001@kernel.dk> (raw)
In-Reply-To: <5A8251503902B84E89CE171AD126BCFB2DE5C66D@NTXBOIMBX01.micron.com>

On 02/17/2015 04:36 PM, Justin Eno (jeno) wrote:
> Hi Jens,
>
> This is a two patch set.
>
> blockalign.patch:
> This patch modifies the behavior of write logging such that *any* overlap
> between a newly-submitted io_piece and elements in the hist_tree results
> in the stale element(s) being evicted and replaced by the new io_piece.
> The current implementation performs replacement only for totally overlapping
> (i.e., aligned) io_pieces.  This restriction causes verification failures
> for random overwrite workloads if blockalign is smaller than blocksize, and
> the patch allows such workloads to succeed.
>
> Note that this changes verification semantics for the specified workload.
> Instead of verifying each written byte, verification for this case covers
> only fully-intact blocks, i.e., remnants of partially-overwritten blocks
> are left unverified.
>
> bsrange.patch:
> This takes advantage of the behavior introduced by blockalign.patch to
> unlock verification of random overwrite workloads with multiple blocksizes.
> The caveat about verification applies here as well, so I've left the warning
> in init.c.

Both of these look good, applied, thanks!

-- 
Jens Axboe



      reply	other threads:[~2015-02-18 18:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18  0:36 [RFC] [PATCH] Allow verification of random overwrites w/ba < bs Justin Eno (jeno)
2015-02-18 18: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=54E4DC17.1080001@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