From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: an iomap-based direct I/O implementation V3
Date: Mon, 28 Nov 2016 10:16:39 +1100 [thread overview]
Message-ID: <20161127231639.GW28177@dastard> (raw)
In-Reply-To: <20161123083657.GA16966@lst.de>
On Wed, Nov 23, 2016 at 09:36:57AM +0100, Christoph Hellwig wrote:
> On Tue, Nov 22, 2016 at 05:40:30PM -0700, Jens Axboe wrote:
> > That's going to be somewhat harder... The REQ_IDLE used to be
> > REQ_NOIDLE. bio_iov_iter_get_pages() is a single commit, so that's easy
> > enough. The poll bits are 3-4 patches, so not too bad either.
>
> I think we'll simply need a tree that has latest master merged into
> the block tree as a base.
I'd prefer not to pull and entire tree into the xfs for-next branch
if I can avoid it.
> The only other option would be to cherry-pick
> bio_iov_iter_get_pages from the block tree into the XFS tree, and I'll
> resend the series so that it doesn't require the other block changes,
> those are fairly mechanical merges that could be carried in linux-next.
I think this is probably a better way of proceeding. Can you resend
the series and in the description indicate what commit I need to
cherrypick from the the block tree?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2016-11-27 23:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 19:07 an iomap-based direct I/O implementation V3 Christoph Hellwig
2016-11-13 19:07 ` [PATCH 1/5] locking/lockdep: Provide a type check for lock_is_held Christoph Hellwig
2016-11-13 19:07 ` [PATCH 2/5] xfs: remove i_iolock and use i_rwsem in the VFS inode instead Christoph Hellwig
2016-11-15 15:34 ` Brian Foster
2016-11-15 16:52 ` Christoph Hellwig
2016-11-13 19:07 ` [PATCH 3/5] fs: make sb_init_dio_done_wq available outside of direct-io.c Christoph Hellwig
2016-11-13 19:07 ` [PATCH 4/5] iomap: implement direct I/O Christoph Hellwig
2016-11-13 19:07 ` [PATCH 5/5] xfs: use iomap_dio_rw Christoph Hellwig
2016-11-15 15:34 ` Brian Foster
2016-11-15 16:52 ` Christoph Hellwig
2016-11-21 16:52 ` an iomap-based direct I/O implementation V3 Christoph Hellwig
2016-11-21 22:34 ` Dave Chinner
2016-11-22 22:52 ` Dave Chinner
2016-11-22 23:12 ` Jens Axboe
2016-11-23 0:02 ` Dave Chinner
2016-11-23 0:40 ` Jens Axboe
2016-11-23 8:36 ` Christoph Hellwig
2016-11-27 23:16 ` Dave Chinner [this message]
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=20161127231639.GW28177@dastard \
--to=david@fromorbit.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@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).