From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: [PATCH 3/3] xfs: allow appending aio writes Date: Tue, 04 Feb 2014 09:24:05 -0800 Message-ID: <20140204172516.819177292@bombadil.infradead.org> References: <20140204172402.380571745@bombadil.infradead.org> Cc: Sergey Meirovich To: xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org Return-path: Received: from bombadil.infradead.org ([198.137.202.9]:42258 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932295AbaBDRZR (ORCPT ); Tue, 4 Feb 2014 12:25:17 -0500 Content-Disposition: inline; filename=0003-xfs-allow-appending-aio-writes.patch Sender: linux-fsdevel-owner@vger.kernel.org List-ID: XFS can easily support appending aio writes by ensuring we always allocate blocks as unwritten extents when performing direct I/O writes and only converting them to written extents at I/O completion. Signed-off-by: Christoph Hellwig --- fs/xfs/xfs_aops.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/fs/xfs/xfs_aops.c b/fs/xfs/xfs_aops.c index a267394..a4278e4 100644 --- a/fs/xfs/xfs_aops.c +++ b/fs/xfs/xfs_aops.c @@ -1441,7 +1441,8 @@ xfs_vm_direct_IO( ret = __blockdev_direct_IO(rw, iocb, inode, bdev, iov, offset, nr_segs, xfs_get_blocks_direct, - xfs_end_io_direct_write, NULL, 0); + xfs_end_io_direct_write, NULL, + DIO_ASYNC_EXTEND); if (ret != -EIOCBQUEUED && iocb->private) goto out_destroy_ioend; } else { -- 1.7.10.4