From: jgmyers@netscape.com (John Myers)
To: Joel Becker <jlbec@evilplan.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-aio@kvack.org" <linux-aio@kvack.org>
Subject: Re: [PATCH 2.5.71-mm1] aio process hang on EINVAL
Date: Wed, 18 Jun 2003 17:33:27 -0700 [thread overview]
Message-ID: <3EF104D7.5050905@netscape.com> (raw)
In-Reply-To: <20030618004214.GK7895@parcelfarce.linux.theplanet.co.uk>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
Joel Becker wrote:
>But POSIX specifes that all detection that can happen before queuing should.
>
The kernel would have to be substantially more complex to report all
errors that could possibly be detected during queuing. The kernel could
even detect success during queuing if it really tried.
This is not a reasonable requirement. A correctly written program has
to be able to handle errors reported asynchronously. Why else would
they be using an asynchronous API?
> You also now require a poll round and aditional system call to
>see the errors. In addition, you waste resources until you pick up the
>errorneous call.
>
So? That is a miniscule amount of resources used by an extremely rare
condition. Such a picayune optimization hardly justifies the necessary
increase in complexity.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3941 bytes --]
next prev parent reply other threads:[~2003-06-19 0:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 0:43 [PATCH 2.5.71-mm1] aio process hang on EINVAL Daniel McNeil
2003-06-17 1:33 ` John Myers
2003-06-17 3:24 ` Suparna Bhattacharya
2003-06-17 18:31 ` John Myers
2003-06-17 21:06 ` Daniel McNeil
2003-06-18 0:03 ` John Myers
2003-06-18 0:15 ` Joel Becker
2003-06-18 0:25 ` John Myers
2003-06-18 0:42 ` Joel Becker
2003-06-19 0:33 ` John Myers [this message]
2003-06-19 0:41 ` Joel Becker
2003-06-19 0:58 ` John Myers
2003-06-19 1:48 ` Scot McKinley
2003-06-19 20:54 ` John Myers
2003-06-19 22:42 ` Scot McKinley
2003-06-18 5:11 ` Scot McKinley
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=3EF104D7.5050905@netscape.com \
--to=jgmyers@netscape.com \
--cc=jlbec@evilplan.org \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
/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