From: Christoph Hellwig <hch@lst.de>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@lst.de>,
linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com,
linux-ext4@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: Re: [PATCH 2/3] xfs: don't use ioends for direct write completions
Date: Mon, 8 Feb 2016 08:31:21 +0100 [thread overview]
Message-ID: <20160208073121.GA30092@lst.de> (raw)
In-Reply-To: <20160208061731.GC27429@dastard>
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.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
Christoph Hellwig <hch@lst.de>,
ocfs2-devel@oss.oracle.com, xfs@oss.sgi.com
Subject: Re: [PATCH 2/3] xfs: don't use ioends for direct write completions
Date: Mon, 8 Feb 2016 08:31:21 +0100 [thread overview]
Message-ID: <20160208073121.GA30092@lst.de> (raw)
In-Reply-To: <20160208061731.GC27429@dastard>
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.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@lst.de>,
linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com,
linux-ext4@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 2/3] xfs: don't use ioends for direct write completions
Date: Mon, 8 Feb 2016 08:31:21 +0100 [thread overview]
Message-ID: <20160208073121.GA30092@lst.de> (raw)
In-Reply-To: <20160208061731.GC27429@dastard>
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.
next prev parent reply other threads:[~2016-02-08 7:31 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 18:40 vfs/xfs: directio updates to ease COW handling V2 Christoph Hellwig
2016-02-03 18:40 ` [Ocfs2-devel] " Christoph Hellwig
2016-02-03 18:40 ` Christoph Hellwig
2016-02-03 18:40 ` [PATCH 1/3] direct-io: always call ->end_io if non-NULL Christoph Hellwig
2016-02-03 18:40 ` [Ocfs2-devel] " Christoph Hellwig
2016-02-03 18:40 ` Christoph Hellwig
2016-02-03 19:55 ` Darrick J. Wong
2016-02-03 19:55 ` [Ocfs2-devel] " Darrick J. Wong
2016-02-03 19:55 ` Darrick J. Wong
2016-02-04 7:14 ` Christoph Hellwig
2016-02-04 7:14 ` [Ocfs2-devel] " Christoph Hellwig
2016-02-04 7:14 ` Christoph Hellwig
2016-02-04 8:17 ` Darrick J. Wong
2016-02-04 8:17 ` [Ocfs2-devel] " Darrick J. Wong
2016-02-04 8:17 ` Darrick J. Wong
2016-02-03 18:40 ` [PATCH 2/3] xfs: don't use ioends for direct write completions Christoph Hellwig
2016-02-03 18:40 ` [Ocfs2-devel] " Christoph Hellwig
2016-02-03 18:40 ` Christoph Hellwig
2016-02-05 21:57 ` Darrick J. Wong
2016-02-05 21:57 ` [Ocfs2-devel] " Darrick J. Wong
2016-02-05 21:57 ` Darrick J. Wong
2016-02-05 22:36 ` Dave Chinner
2016-02-05 22:36 ` [Ocfs2-devel] " Dave Chinner
2016-02-05 22:36 ` Dave Chinner
2016-02-08 1:00 ` Dave Chinner
2016-02-08 1:00 ` [Ocfs2-devel] " Dave Chinner
2016-02-08 1:00 ` Dave Chinner
2016-02-08 6:17 ` Dave Chinner
2016-02-08 6:17 ` [Ocfs2-devel] " Dave Chinner
2016-02-08 6:17 ` Dave Chinner
2016-02-08 7:31 ` Christoph Hellwig [this message]
2016-02-08 7:31 ` [Ocfs2-devel] " Christoph Hellwig
2016-02-08 7:31 ` Christoph Hellwig
2016-02-08 9:16 ` Dave Chinner
2016-02-08 9:16 ` [Ocfs2-devel] " Dave Chinner
2016-02-08 9:16 ` Dave Chinner
2016-02-08 9:22 ` Christoph Hellwig
2016-02-08 9:22 ` [Ocfs2-devel] " Christoph Hellwig
2016-02-08 9:22 ` Christoph Hellwig
2016-02-03 18:40 ` [PATCH 3/3] xfs: fold xfs_vm_do_dio into xfs_vm_direct_IO Christoph Hellwig
2016-02-03 18:40 ` [Ocfs2-devel] " Christoph Hellwig
2016-02-03 18:40 ` Christoph Hellwig
2016-02-03 18:40 ` Christoph Hellwig
2016-02-03 19:43 ` vfs/xfs: directio updates to ease COW handling V2 Jeff Moyer
2016-02-03 19:43 ` [Ocfs2-devel] " Jeff Moyer
2016-02-03 19:43 ` Jeff Moyer
2016-02-03 20:01 ` Darrick J. Wong
2016-02-03 20:01 ` [Ocfs2-devel] " Darrick J. Wong
2016-02-03 20:01 ` Darrick J. Wong
2016-02-03 21:53 ` Jeff Moyer
2016-02-03 21:53 ` [Ocfs2-devel] " Jeff Moyer
2016-02-03 21:53 ` Jeff Moyer
-- strict thread matches above, loose matches on Subject: below --
2016-02-02 20:17 VFS/XFS: directio updates to ease COW handling Christoph Hellwig
2016-02-02 20:17 ` [PATCH 2/3] xfs: don't use ioends for direct write completions Christoph Hellwig
2016-02-02 20:17 ` Christoph Hellwig
2016-02-03 13:52 ` Brian Foster
2016-02-03 13:52 ` Brian Foster
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=20160208073121.GA30092@lst.de \
--to=hch@lst.de \
--cc=david@fromorbit.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.