From: Suparna Bhattacharya <suparna@in.ibm.com>
Currently, the high level AIO code keeps issuing retries until the
entire transfer is done, i.e. until all the bytes requested are
read (See aio_pread), which is what we needed for filesystem aio
read. However, in the pipe read case, the expected semantics would
be to return as soon as it has any bytes transferred, rather than
waiting for the entire transfer. This will also be true in for
network aio reads if/when we implement it.
Hmm, so we need to get the generic code to allow for this
possibility - maybe based on a check for ISFIFO/ISSOCK ?
aio.c | 12 ++++++++++--
1 files changed, 10 insertions(+), 2 deletions(-)
--- aio/fs/aio.c 2004-06-18 09:31:00.795414792 -0700
+++ aio-read-immediate/fs/aio.c 2004-06-18 09:31:39.459536952 -0700
@@ -1272,6 +1272,8 @@ asmlinkage long sys_io_destroy(aio_conte
static ssize_t aio_pread(struct kiocb *iocb)
{
struct file *file = iocb->ki_filp;
+ struct address_space *mapping = file->f_mapping;
+ struct inode *inode = mapping->host;
ssize_t ret = 0;
ret = file->f_op->aio_read(iocb, iocb->ki_buf,
@@ -1284,8 +1286,14 @@ static ssize_t aio_pread(struct kiocb *i
if (ret > 0) {
iocb->ki_buf += ret;
iocb->ki_left -= ret;
-
- ret = -EIOCBRETRY;
+ /*
+ * For pipes and sockets we return once we have
+ * some data; for regular files we retry till we
+ * complete the entire read or find that we can't
+ * read any more data (e.g short reads).
+ */
+ if (!S_ISFIFO(inode->i_mode) && !S_ISSOCK(inode->i_mode))
+ ret = -EIOCBRETRY;
}
/* This means we must have transferred all that we could */