From: Phillip Susi <psusi@cfl.rr.com>
To: "Raz Ben-Jehuda(caro)" <raziebe@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, linux-aio@kvack.org
Subject: Re: slow io_submit
Date: Tue, 05 Dec 2006 16:18:47 -0500 [thread overview]
Message-ID: <4575E237.9090902@cfl.rr.com> (raw)
In-Reply-To: <5d96567b0612050823n225d4c43j35c7210e228d26@mail.gmail.com>
Raz Ben-Jehuda(caro) wrote:
> thanks Phiilip
> But... hmmm ... should'nt an asynchronous operation act as
> "send and forget" . isn't "queue full" a problem that aio must at
> least try and handle before returning to the user ?
It is handling it; by blocking until the queue is not full. A better
way of handling it would be to return in such a way that the caller
knows the queue is full and needs to wait before it can submit more
requests, possibly doing some computation or submitting requests to
other devices in the mean time.
prev parent reply other threads:[~2006-12-05 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 17:04 slow io_submit Raz Ben-Jehuda(caro)
2006-12-01 17:27 ` Jens Axboe
2006-12-01 21:40 ` Raz Ben-Jehuda(caro)
2006-12-04 15:38 ` Phillip Susi
2006-12-05 16:23 ` Raz Ben-Jehuda(caro)
2006-12-05 21:18 ` Phillip Susi [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=4575E237.9090902@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raziebe@gmail.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