From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f47.google.com ([74.125.82.47]:36989 "EHLO mail-wm0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755486AbcKESOS (ORCPT ); Sat, 5 Nov 2016 14:14:18 -0400 Received: by mail-wm0-f47.google.com with SMTP id t79so106029099wmt.0 for ; Sat, 05 Nov 2016 11:14:18 -0700 (PDT) Subject: Re: [PATCH 4/5] iomap: implement direct I/O To: Christoph Hellwig , linux-xfs@vger.kernel.org References: <1478276479-10749-1-git-send-email-hch@lst.de> <1478276479-10749-5-git-send-email-hch@lst.de> Cc: axboe@fb.com, kent.overstreet@gmail.com, linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org From: Avi Kivity Message-ID: <2dabe3ec-193b-3ecf-af5c-a5ba976de6eb@scylladb.com> Date: Sat, 5 Nov 2016 20:14:14 +0200 MIME-Version: 1.0 In-Reply-To: <1478276479-10749-5-git-send-email-hch@lst.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hello, On 11/04/2016 06:21 PM, Christoph Hellwig wrote: > This adds a full fledget direct I/O implementation using the iomap > interface. Full fledged in this case means all features are supported: > AIO, vectored I/O, any iov_iter type including kernel pointers, bvecs > and pipes, support for hole filling and async apending writes. Does this include support for more than one concurrent appending write for the same file? If so, that's great, but please make this feature discoverable. Right now applications have to benchmark or guess how fully asynchronous the aio implementation is.