Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751540AbaLaVxY (ORCPT ); Wed, 31 Dec 2014 16:53:24 -0500 Received: from userp1040.oracle.com ([156.151.31.81]:20814 "EHLO userp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751080AbaLaVxX (ORCPT ); Wed, 31 Dec 2014 16:53:23 -0500 Message-ID: <54A4703B.2000006@oracle.com> Date: Wed, 31 Dec 2014 15:52:59 -0600 From: Dave Kleikamp User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: sedat.dilek@gmail.com CC: LKML , linux-fsdevel , Andrew Morton , "Maxim V. Patlasov" , Zach Brown , Ming Lei Subject: Re: [PATCH V8 00/33] loop: Issue O_DIRECT aio using bio_vec References: <1374774659-13121-1-git-send-email-dave.kleikamp@oracle.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Source-IP: acsinet22.oracle.com [141.146.126.238] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1016 Lines: 25 On 12/31/2014 02:38 PM, Sedat Dilek wrote: > > What has happened to that aio_loop patchset? > Is it in Linux-next? > ( /me started to play with "block: loop: convert to blk-mq (v3)", so I > recalled this other improvement. ) It met with some harsh resistance, so I backed off on it. Then Al Viro got busy re-writing the iov_iter infrastructure and I put my patchset on the shelf to look at later. Then Ming Lei submitted more up-to-date patchset: https://lkml.org/lkml/2014/8/6/175 It looks like Ming is currently only pushing the first half of that patchset. I don't know what his plans are for the last three patches: aio: add aio_kernel_() interface fd/direct-io: introduce should_dirty for kernel aio block: loop: support to submit I/O via kernel aio based Dave -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/