From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-fsdevel@vger.kernel.org,
Sergey Meirovich <rathamahata@gmail.com>,
xfs@oss.sgi.com
Subject: Re: [PATCH 0/3] support appending AIO writes
Date: Wed, 5 Feb 2014 09:29:01 +1100 [thread overview]
Message-ID: <20140204222901.GE13997@dastard> (raw)
In-Reply-To: <20140204172402.380571745@bombadil.infradead.org>
On Tue, Feb 04, 2014 at 09:24:02AM -0800, Christoph Hellwig wrote:
> At least XFS can support appending AIO writes easily, and Sergey has
> demonstrated a use case for them.
>
> I've not done any performance testing myself, but ensured that xfstests
> already exercises the code path.
The patches look sane. Does the dio change conflict with the
work Al is doing right now of the direct IO path, or will
marshalling that part of the change through the XFS tree be fine?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-02-04 22:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 17:24 [PATCH 0/3] support appending AIO writes Christoph Hellwig
2014-02-04 17:24 ` [PATCH 1/3] direct-io: add flag to allow aio writes beyond i_size Christoph Hellwig
2014-02-04 17:24 ` [PATCH 2/3] xfs: always use unwritten extents for direct I/O writes Christoph Hellwig
2014-02-04 17:24 ` [PATCH 3/3] xfs: allow appending aio writes Christoph Hellwig
2014-02-04 22:29 ` Dave Chinner [this message]
2014-02-05 6:57 ` [PATCH 0/3] support appending AIO writes Christoph Hellwig
2014-02-05 7:59 ` Dave Chinner
2014-02-05 13:55 ` Al Viro
2014-02-05 14:52 ` Sergey Meirovich
2014-02-06 16:29 ` Sergey Meirovich
2014-02-06 22:51 ` Dave Chinner
2014-02-07 9:40 ` Sergey Meirovich
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=20140204222901.GE13997@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rathamahata@gmail.com \
--cc=xfs@oss.sgi.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).