From: Jens Axboe <jaxboe@fusionio.com>
To: Steven Lang <tirea@google.com>
Cc: fio@vger.kernel.org
Subject: Re: Asynch IO and fill_device
Date: Mon, 13 Jun 2011 09:48:18 +0200 [thread overview]
Message-ID: <4DF5C0C2.1050300@fusionio.com> (raw)
In-Reply-To: <BANLkTi=LKqCz1Pg0w3Pk8i2OzgHcQFat4A@mail.gmail.com>
On 2011-06-10 21:05, Steven Lang wrote:
> I found an interesting combination of using fill_device when the
> iodepth is greater than 1. All outstanding IO causes an ENOSPC error,
> but only the first is treated specially. The remainder come through
> and cause an error exit condition when the IO queue is being cleared.
> So it is impossible to use deep IO with fill device.
>
> This patch should fix the issue.
Thanks, applied.
--
Jens Axboe
prev parent reply other threads:[~2011-06-13 7:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 19:05 Asynch IO and fill_device Steven Lang
2011-06-13 7:48 ` 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=4DF5C0C2.1050300@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=fio@vger.kernel.org \
--cc=tirea@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 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.