From: Jeff Moyer <jmoyer@redhat.com>
To: Zubin Dittia <zubin@tintri.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: libaio asynchronous syscall io_getevents blocks on error
Date: Tue, 20 Oct 2009 19:59:04 -0400 [thread overview]
Message-ID: <x4963a9obw7.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <47c554d90910201634n68b359c1n501ed5669deb07be@mail.gmail.com> (Zubin Dittia's message of "Tue, 20 Oct 2009 16:34:04 -0700")
Zubin Dittia <zubin@tintri.com> writes:
> But this does bring up the interesting question of how to know which
> of the I/Os I submitted had an error, and what the error was. Does it
If io_submit returned N, then the N+1 iocb had an error.
> PS: It does seem a little strange that io_submit returns an error if
> the first IOCB is invalid but not when any of the other IOCBs are
> invalid (this appears to be the case, at least according to the man
> page).
It makes sense that it tells you how many it could successfully submit.
If it can't submit any, you get the error from the first I/O.
Cheers,
Jeff
next prev parent reply other threads:[~2009-10-20 23:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 21:58 Zubin Dittia
2009-10-20 22:25 ` Jeff Moyer
2009-10-20 23:34 ` Zubin Dittia
2009-10-20 23:59 ` Jeff Moyer [this message]
2009-10-21 0:10 ` Zubin Dittia
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=x4963a9obw7.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zubin@tintri.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
all inboxes | Powered by JetHome®