Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Juan Casse <jcasse@google.com>
Cc: Juan Casse <jcasse@chromium.org>,
	Grant Grundler <grundler@chromium.org>,
	"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: [PATCH] Adds verify_only option.
Date: Sat, 7 Sep 2013 19:32:03 -0600	[thread overview]
Message-ID: <20130908013203.GJ31170@kernel.dk> (raw)
In-Reply-To: <CAPet_21-oPZ2bEQw_Uwq2GdM4T5HNUcN2eqTPifqRpCSEE-_cA@mail.gmail.com>

On Fri, Sep 06 2013, Juan Casse wrote:
> On Fri, Sep 6, 2013 at 7:46 AM, Jens Axboe <axboe@kernel.dk> wrote:
> ...
> > Please take a look at how this is done for the experimental_verify. The
> > writes are skipped much sooner and generically, there's no need to
> > enforce any sort of specific IO engine or verify type.
> 
> From your reply I understood that you want to skip do_io() all
> together and call a function that will somehow replicate the workload
> and compute the numberio for each block. Is that what you meant?

Yes, you want the logic to be in the realm of do_verify(). See the
experimental verify. It basically rewinds the various random/lfsr dials
and replays, skips writes, etc.

> My patch uses do_io() to initialize the vhdr_meta data structures. I
> can try to replicate that in do_verify() instead, but that seems more
> fragile.

Honestly, at this point, not sure what change you are trying to
accomplish there... But if you send your suggested change, I'll take a
look and comment.

If not, please step back a bit and explain to me exactly which logic you
are looking for. I think that will help both of us and will get us to a
better place on the implementation and changes.

-- 
Jens Axboe


      reply	other threads:[~2013-09-08  1:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-06  3:12 [PATCH] Adds verify_only option Juan Casse
2013-09-06 14:46 ` Jens Axboe
2013-09-06 17:15   ` Grant Grundler
2013-09-06 23:31   ` Juan Casse
2013-09-08  1:32     ` 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=20130908013203.GJ31170@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=grundler@chromium.org \
    --cc=jcasse@chromium.org \
    --cc=jcasse@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