From: Jens Axboe <axboe@kernel.dk>
To: "Bruce Cran" <bruce@cran.org.uk>,
"Sébastien Bouchex Bellomié" <sbouchex@infovista.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>,
bcran@fusionio.com
Subject: Re: ioengine=sync issue on Windows
Date: Thu, 03 Apr 2014 20:17:31 -0600 [thread overview]
Message-ID: <533E163B.2080605@kernel.dk> (raw)
In-Reply-To: <533E1590.1070109@cran.org.uk>
On 2014-04-03 20:14, Bruce Cran wrote:
>
> On 4/3/2014 7:57 PM, Jens Axboe wrote:
>> On 2014-04-03 16:42, Bruce Cran wrote:
>>>
>>> Also, fio-2.0.15 works, while fio-2.1 doesn't.
>>
>> That makes very little sense... How could the contents of the buffer
>> change the behavior?
>>
>> Could you run a git bisect? Should be quick'n easy, if it's nicely
>> reproducible.
>>
>
> http://git.kernel.dk/?p=fio.git;a=commit;h=cc86c395fd9dd2002ec1edc0967b7c9453debdfb
> is the changeset that breaks things - and I know it makes no sense.
That is pretty nutty. If you revert just the change to filesetup.c, does
that make it work again?
--
Jens Axboe
next prev parent reply other threads:[~2014-04-04 2:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 15:41 ioengine=sync issue on Windows Sébastien Bouchex Bellomié
2014-03-12 16:33 ` Jens Axboe
2014-03-12 17:48 ` Bruce Cran
2014-03-12 18:02 ` Bruce Cran
2014-03-12 19:11 ` Jens Axboe
2014-03-12 19:24 ` Bruce Cran
2014-03-12 19:30 ` Jens Axboe
2014-03-12 19:36 ` Bruce Cran
2014-03-12 19:38 ` Jens Axboe
2014-03-12 19:41 ` Jens Axboe
2014-03-12 19:44 ` Bruce Cran
2014-04-02 3:11 ` Bruce Cran
2014-04-03 22:42 ` Bruce Cran
2014-04-04 1:57 ` Jens Axboe
2014-04-04 2:14 ` Bruce Cran
2014-04-04 2:17 ` Jens Axboe [this message]
2014-04-04 2:26 ` Bruce Cran
2014-04-04 2:35 ` Jens Axboe
2014-04-04 3:12 ` Bruce Cran
2014-04-04 3:28 ` Jens Axboe
2014-04-28 22:04 ` Bruce Cran
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=533E163B.2080605@kernel.dk \
--to=axboe@kernel.dk \
--cc=bcran@fusionio.com \
--cc=bruce@cran.org.uk \
--cc=fio@vger.kernel.org \
--cc=sbouchex@infovista.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.