From: Badari Pulavarty <pbadari@us.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: akpm@osdl.org, hch@lst.de, pbadari@us.ibm.com,
Zach Brown <zach.brown@oracle.com>,
cel@citi.umich.edu
Subject: [PATCH 0/4] VFS fileop cleanups by collapsing AIO and vector IO (2.6.17-rc5-mm2)
Date: Fri, 02 Jun 2006 12:06:33 -0700 [thread overview]
Message-ID: <1149275193.26170.8.camel@dyn9047017100.beaverton.ibm.com> (raw)
Hi Andrew,
Here is the updated set of patches for 2.6.17-rc5-mm2 with
autofs fixes. Ian and I verified with autofs tests and also
running on Fedora Core 5. I made the series against latest
-mm since, there are bunch of tweaks needed to suite -mm
(I didn't want to put you through the pain of doing it yourself).
If you prefer against mainline (2.6.17-rc5), let me know -
I can post that set as well.
Hopefully, 18th time is the charm :)
===========
These series of patches clean up and streamlines generic_file_*
interfaces in filemap.c.
First (3) patches collapses all the vectored IO support into
single set of file-operation method using aio_read/aio_write.
This work was originally suggested & started by Christoph Hellwig,
when Zach Brown tried to add vectored support for AIO.
Patch 4, sets all the filesystems .read/.write/.aio_read/.aio_write
methods correctly to allow us to cleanup most generic_file_*_read/write
interfaces in filemap.c
After this patch set, we should end up with ONLY following
read/write (exported) interfaces in filemap.c:
generic_file_aio_read() - read handler
generic_file_aio_write() - write handler
generic_file_aio_write_nolock() - no lock write handler
Here is the summary:
[PATCH 1/4] Vectorize aio_read/aio_write methods
[PATCH 2/4] Remove readv/writev methods and use aio_read/aio_write
instead.
[PATCH 3/4] Core aio changes to support vectored AIO.
[PATCH 4/4] Streamline generic_file_* interfaces and filemap cleanups
BTW, Chuck Lever is actually re-arranging NFS DIO, AIO code to
fit into this model.
Thanks,
Badari
next reply other threads:[~2006-06-02 19:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 19:06 Badari Pulavarty [this message]
2006-06-02 19:07 ` [PATCH 1/4] Vectorize aio_read/aio_write methods Badari Pulavarty
2006-06-02 19:08 ` [PATCH 2/4] Remove readv/writev methods and use aio_read/aio_write instead Badari Pulavarty
2006-06-02 19:10 ` [PATCH 3/4] Core aio changes to support vectored AIO Badari Pulavarty
2006-06-02 19:10 ` [PATCH 4/4] Streamline generic_file_* interfaces and filemap cleanups Badari Pulavarty
2006-06-02 21:38 ` [PATCH 0/4] VFS fileop cleanups by collapsing AIO and vector IO (2.6.17-rc5-mm2) 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=1149275193.26170.8.camel@dyn9047017100.beaverton.ibm.com \
--to=pbadari@us.ibm.com \
--cc=akpm@osdl.org \
--cc=cel@citi.umich.edu \
--cc=hch@lst.de \
--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).