From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay3.corp.sgi.com [198.149.34.15]) by oss.sgi.com (Postfix) with ESMTP id 30A8B7CA2 for ; Mon, 8 Feb 2016 03:22:05 -0600 (CST) Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by relay3.corp.sgi.com (Postfix) with ESMTP id B37A3AC001 for ; Mon, 8 Feb 2016 01:22:04 -0800 (PST) Received: from newverein.lst.de (verein.lst.de [213.95.11.211]) by cuda.sgi.com with ESMTP id KPF1ACE4uNFPdLws (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 08 Feb 2016 01:22:02 -0800 (PST) Date: Mon, 8 Feb 2016 10:22:00 +0100 From: Christoph Hellwig Subject: Re: [PATCH 2/3] xfs: don't use ioends for direct write completions Message-ID: <20160208092200.GA31881@lst.de> References: <1454524816-11392-1-git-send-email-hch@lst.de> <1454524816-11392-3-git-send-email-hch@lst.de> <20160208010026.GL31407@dastard> <20160208061731.GC27429@dastard> <20160208073121.GA30092@lst.de> <20160208091644.GD27429@dastard> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20160208091644.GD27429@dastard> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Dave Chinner Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org, ocfs2-devel@oss.oracle.com, xfs@oss.sgi.com On Mon, Feb 08, 2016 at 08:16:44PM +1100, Dave Chinner wrote: > I can't tell if you are saying what I've done is fine if the > xfs-dio-fix-4.6 branch is stable (so others can pull it) or whether > it should be in some other tree. Can you clarify, Christoph? What you are doing is fine, thanks! _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs