From: Omar Sandoval <osandov@osandov.com>
To: Klaus Birkelund Jensen <its@irrelevant.dk>
Cc: Klaus Jensen <k.jensen@samsung.com>,
linux-block@vger.kernel.org, osandov@fb.com
Subject: Re: [PATCH blktests] common/fio: do not use norandommap with verify
Date: Fri, 3 Apr 2020 11:20:36 -0700 [thread overview]
Message-ID: <20200403182036.GB189126@vader> (raw)
In-Reply-To: <20200402112458.bpcadafgkqf6eq6j@apples.localdomain>
On Thu, Apr 02, 2020 at 01:25:09PM +0200, Klaus Birkelund Jensen wrote:
> On Feb 3 13:43, Omar Sandoval wrote:
> > On Thu, Jan 30, 2020 at 09:49:41AM +0100, Klaus Jensen wrote:
> > > As per the fio documentation, using norandommap with an async I/O engine
> > > and I/O depth > 1, can cause verification errors.
> > >
> > > Signed-off-by: Klaus Jensen <k.jensen@samsung.com>
> >
> > Good catch, applied. Thanks!
>
> Hi Omar,
>
> Looks like this got lost somewhere?
You're right, not sure what happened there. Applied and pushed this
time.
prev parent reply other threads:[~2020-04-03 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200130084950eucas1p2dac69024658d531d5f69ea0bdbd2be81@eucas1p2.samsung.com>
2020-01-30 8:49 ` [PATCH blktests] common/fio: do not use norandommap with verify Klaus Jensen
2020-02-03 21:43 ` Omar Sandoval
2020-04-02 11:25 ` Klaus Birkelund Jensen
2020-04-03 18:20 ` Omar Sandoval [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=20200403182036.GB189126@vader \
--to=osandov@osandov.com \
--cc=its@irrelevant.dk \
--cc=k.jensen@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=osandov@fb.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