From: Bruce Cran <bruce@cran.org.uk>
To: "Jens Axboe" <axboe@kernel.dk>,
"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: Mon, 28 Apr 2014 16:04:57 -0600 [thread overview]
Message-ID: <535ED089.9000707@cran.org.uk> (raw)
In-Reply-To: <533E26C9.9040609@kernel.dk>
On 4/3/2014 9:28 PM, Jens Axboe wrote:
> This really sounds like an issue with write() on windows. The change
> looks fine, and the fact that moving the memset around makes a
> difference - well, that's just bizarre. Do you have time to dig into
> this? Was read/write really completely reliable before this change?
It turns out it was a problem with open() - you need to pass _O_BINARY
to avoid Windows trying to interpret file contents.
--
Bruce
prev parent reply other threads:[~2014-04-28 22:04 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
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 [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=535ED089.9000707@cran.org.uk \
--to=bruce@cran.org.uk \
--cc=axboe@kernel.dk \
--cc=bcran@fusionio.com \
--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.