From: Bruce Cran <bruce@cran.org.uk>
To: Jens Axboe <axboe@kernel.dk>
Cc: "Jeffrey McVay (jmcvay)" <jmcvay@micron.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: FIO 2.0.9 for Windows Server 2008 RC1 SP2 reports extreme latencies
Date: Wed, 10 Oct 2012 15:18:09 +0100 [thread overview]
Message-ID: <507583A1.9030308@cran.org.uk> (raw)
In-Reply-To: <50758306.7020807@kernel.dk>
On 10/10/2012 15:15, Jens Axboe wrote:
> So where is this bug exactly? Is Windows reaping events from the head of
> this list, and thus starving indefinitely potentially?
Yes - both windowsaio and posixaio read from the head of the list.
--
Bruce Cran
next prev parent reply other threads:[~2012-10-10 14:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 5:41 FIO 2.0.9 for Windows Server 2008 RC1 SP2 reports extreme latencies Jeffrey McVay (jmcvay)
2012-09-24 13:28 ` Bruce Cran
2012-09-26 16:30 ` Jeffrey McVay (jmcvay)
2012-09-26 16:32 ` Bruce Cran
2012-09-29 6:23 ` Jens Axboe
2012-09-29 13:46 ` Bruce Cran
2012-09-29 14:21 ` Jens Axboe
2012-10-06 0:25 ` Jeffrey McVay (jmcvay)
2012-10-10 10:07 ` Bruce Cran
2012-10-10 10:41 ` Bruce Cran
2012-10-10 14:15 ` Jens Axboe
2012-10-10 14:18 ` Bruce Cran [this message]
2012-10-10 14:19 ` Jens Axboe
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=507583A1.9030308@cran.org.uk \
--to=bruce@cran.org.uk \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=jmcvay@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