xfs
[Top] [All Lists]

Re: [PATCH 2/3] xfs: don't use ioends for direct write completions

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: [PATCH 2/3] xfs: don't use ioends for direct write completions
From: Christoph Hellwig <hch@xxxxxx>
Date: Mon, 8 Feb 2016 08:31:21 +0100
Cc: Christoph Hellwig <hch@xxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, ocfs2-devel@xxxxxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20160208061731.GC27429@dastard>
References: <1454524816-11392-1-git-send-email-hch@xxxxxx> <1454524816-11392-3-git-send-email-hch@xxxxxx> <20160208010026.GL31407@dastard> <20160208061731.GC27429@dastard>
User-agent: Mutt/1.5.17 (2007-11-01)
On Mon, Feb 08, 2016 at 05:17:31PM +1100, Dave Chinner wrote:
> Right now this series is in a stable branch in the XFS tree:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git 
> xfs-dio-fix-4.6
> 
> If you want to push it through some other tree, please let me know
> when/where it is committed so I can rebuild the XFS for-next branch
> appropriately from a stable commit/branch...

That's how I think it should be handled.  This would also allow the
ext4 and ocfs2 maintainers to depend on the stable branch to clean
up their direct I/O completion handling in this merge window if they
want to.

<Prev in Thread] Current Thread [Next in Thread>