Re: an iomap-based direct I/O implementation V3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux