From: Badari Pulavarty <pbadari@us.ibm.com>
To: christoph <hch@lst.de>, Benjamin LaHaise <bcrl@kvack.org>,
Zach Brown <zach.brown@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
pbadari@us.ibm.com
Subject: [PATCH 0/3] VFS changes to collapse all the vectored and AIO support
Date: Thu, 02 Feb 2006 08:12:38 -0800 [thread overview]
Message-ID: <1138896758.28382.112.camel@dyn9047017102.beaverton.ibm.com> (raw)
Hi,
This work was originally suggested & started by Christoph Hellwig,
when Zack Brown tried to add vectored support for AIO. These series
of changes collapses all the vectored IO support into single
file-operation method using aio_read/aio_write.
Christoph & Zack, comments/suggestions ? If you are happy with the
work, can you add your Sign-off or Ack ?
Here is the summary:
[PATCH 1/3] Vectorize aio_read/aio_write methods
[PATCH 2/3] Remove readv/writev methods and use aio_read/aio_write
instead.
[PATCH 3/3] Zack's core aio changes to support vectored AIO.
To Do/Issues:
1) Since aio_read/aio_write are vectorized now, need to modify
nfs AIO+DIO and usb/gadget to handle vectors. Is it needed ?
For now, it handles only single vector. Christoph, should I
loop over all the vectors ?
2) AIO changes need careful review & could be cleaned up further.
Zack, can you take a look at those ?
3) Ben's suggestion of kernel iovec to hold precomputed information
(like total iolen) instead of computing every time.
Thanks,
Badari
next reply other threads:[~2006-02-02 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 16:12 Badari Pulavarty [this message]
2006-02-02 16:14 ` [PATCH 1/3] Vectorize aio_read/aio_write methods Badari Pulavarty
2006-02-04 13:28 ` Christoph Hellwig
2006-02-04 22:10 ` Badari Pulavarty
2006-02-02 16:15 ` [PATCH 2/3] Remove readv/writev methods and use aio_read/aio_write instead Badari Pulavarty
2006-02-02 16:16 ` [PATCH 3/3] Zack's core aio changes to support vectored AIO Badari Pulavarty
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=1138896758.28382.112.camel@dyn9047017102.beaverton.ibm.com \
--to=pbadari@us.ibm.com \
--cc=bcrl@kvack.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zach.brown@oracle.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;
as well as URLs for NNTP newsgroup(s).