From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org,
Sergey Meirovich <rathamahata@gmail.com>,
xfs@oss.sgi.com
Subject: Re: [PATCH 0/3] support appending AIO writes
Date: Tue, 4 Feb 2014 22:57:28 -0800 [thread overview]
Message-ID: <20140205065728.GA30899@infradead.org> (raw)
In-Reply-To: <20140204222901.GE13997@dastard>
On Wed, Feb 05, 2014 at 09:29:01AM +1100, Dave Chinner wrote:
> 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?
I've not seen any changes in that area in Al's trees. That being said
I don't think this little flag should cause any major problems as we'll
have to pass the flags argument in some form of direct I/O method for
all the other quirks we have.
next prev parent reply other threads:[~2014-02-05 6:57 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 ` [PATCH 0/3] support appending AIO writes Dave Chinner
2014-02-05 6:57 ` Christoph Hellwig [this message]
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=20140205065728.GA30899@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--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).