From: Benjamin LaHaise <bcrl@redhat.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Jens Axboe <axboe@suse.de>,
Suparna Bhattacharya <suparna@in.ibm.com>,
Shailabh Nagar <nagar@watson.ibm.com>,
Linux Aio <linux-aio@kvack.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.5 port of aio-20020619 for raw devices
Date: Fri, 13 Sep 2002 15:57:44 -0400 [thread overview]
Message-ID: <20020913155744.C2969@redhat.com> (raw)
In-Reply-To: <3D823DCC.3E303941@digeo.com>; from akpm@digeo.com on Fri, Sep 13, 2002 at 12:34:36PM -0700
On Fri, Sep 13, 2002 at 12:34:36PM -0700, Andrew Morton wrote:
> It has the disadvantage that we may have some data which is mergeable,
> and would in fact nonblockingly fit into a "congested" queue. Don't
> know if that makes a lot of difference in practice.
That's what I was thinking. Not having a congested queue really breaks
aio as your submit point is not supposed to incur significant latency: an
io should -EAGAIN if it would cost a large delay to setup.
-ben
--
"You will be reincarnated as a toad; and you will be much happier."
next prev parent reply other threads:[~2002-09-13 19:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 18:21 [PATCH] 2.5 port of aio-20020619 for raw devices Shailabh Nagar
2002-09-12 18:35 ` Benjamin LaHaise
2002-09-12 18:37 ` Shailabh Nagar
2002-09-12 18:53 ` Benjamin LaHaise
2002-09-12 19:31 ` Shailabh Nagar
2002-09-12 19:40 ` Benjamin LaHaise
2002-09-13 13:16 ` Suparna Bhattacharya
2002-09-13 13:44 ` Jens Axboe
2002-09-13 19:34 ` Andrew Morton
2002-09-13 19:57 ` Benjamin LaHaise [this message]
2002-09-13 20:03 ` Andrew Morton
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=20020913155744.C2969@redhat.com \
--to=bcrl@redhat.com \
--cc=akpm@digeo.com \
--cc=axboe@suse.de \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nagar@watson.ibm.com \
--cc=suparna@in.ibm.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;
as well as URLs for NNTP newsgroup(s).