From: Benjamin LaHaise <bcrl@redhat.com>
To: Christoph Hellwig <hch@sgi.com>,
akpm@digeo.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-aio@kvack.org
Subject: Re: [RFC] iovec in ->aio_read/->aio_write
Date: Tue, 15 Oct 2002 15:34:27 -0400 [thread overview]
Message-ID: <20021015153427.A16156@redhat.com> (raw)
In-Reply-To: <20021015223315.A21139@sgi.com>; from hch@sgi.com on Tue, Oct 15, 2002 at 10:33:15PM -0400
On Tue, Oct 15, 2002 at 10:33:15PM -0400, Christoph Hellwig wrote:
> Proposed next steps: Convert over all readv/writev users
> to aio_read/aio_write and remove the methods. Implement
> aio_read/aio_write in all filesystems using the generic
> pagecache code and kill the "normal" generic_file_read
> and generic_file_write.
>
> Comments?
Please not right now? ;-) At least introduce it as aio_readv/aio_writev
as currently the way we deal with iovecs uglifies a lot of code, with no
benefit for the vast majority of applications. As for killing
generic_file_read/write and using the aio counterparts, that is the plan
pending a bit more testing of things. I want to get there step by step
without breaking everything along the way.
-ben
--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to majordomo@kvack.org. For more info on Linux AIO,
see: http://www.kvack.org/aio/
next prev parent reply other threads:[~2002-10-15 19:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 2:33 [RFC] iovec in ->aio_read/->aio_write Christoph Hellwig
2002-10-15 19:34 ` Benjamin LaHaise [this message]
2002-10-16 6:51 ` Janet Morgan
2002-10-16 13:41 ` Shailabh Nagar
2002-10-16 15:06 ` Benjamin LaHaise
2002-10-17 11:22 ` Janet Morgan
-- strict thread matches above, loose matches on Subject: below --
2002-10-16 14:40 Helen Pang
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=20021015153427.A16156@redhat.com \
--to=bcrl@redhat.com \
--cc=akpm@digeo.com \
--cc=hch@sgi.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 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).