From: Matthew Wilcox <matthew@wil.cx>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: Jamie Lokier <jamie@shareable.org>,
Christoph Hellwig <hch@lst.de>,
akpm@osdl.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] add support for vectored and async I/O to all simple filesystems
Date: Wed, 2 Nov 2005 09:29:04 -0700 [thread overview]
Message-ID: <20051102162904.GK23749@parisc-linux.org> (raw)
In-Reply-To: <20051102162107.GA32755@kvack.org>
On Wed, Nov 02, 2005 at 11:21:07AM -0500, Benjamin LaHaise wrote:
> On Wed, Nov 02, 2005 at 11:06:30AM +0000, Jamie Lokier wrote:
> > So it means that any program that mustn't block, must now have a
> > stupid kernel version check to make sure it avoids even trying aio
> > system calls? I was under the impression that the right thing to do
> > so far was try them, and when EINVAL is returned, use threads instead.
>
> Yes, that is correct.
To be fair, the aio system calls were never _guaranteed_ to not block,
were they? ISTR there were various corner cases that would still get
your task blocking while doing an aio submission.
next prev parent reply other threads:[~2005-11-02 16:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 2:36 [PATCH] add support for vectored and async I/O to all simple filesystems Christoph Hellwig
2005-11-01 10:28 ` Miklos Szeredi
2005-11-01 15:27 ` Christoph Hellwig
2005-11-01 17:19 ` Miklos Szeredi
2005-11-07 5:00 ` Christoph Hellwig
2005-11-01 19:20 ` Jamie Lokier
2005-11-01 20:57 ` Benjamin LaHaise
2005-11-02 11:06 ` Jamie Lokier
2005-11-02 16:21 ` Benjamin LaHaise
2005-11-02 16:29 ` Matthew Wilcox [this message]
2005-11-02 16:45 ` Benjamin LaHaise
2005-11-02 20:31 ` Jamie Lokier
2005-11-02 21:04 ` Anton Altaparmakov
2005-11-02 23:36 ` Jamie Lokier
2005-11-05 0:18 ` Christoph Hellwig
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=20051102162904.GK23749@parisc-linux.org \
--to=matthew@wil.cx \
--cc=akpm@osdl.org \
--cc=bcrl@kvack.org \
--cc=hch@lst.de \
--cc=jamie@shareable.org \
--cc=linux-fsdevel@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 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.