From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ted Ts'o Subject: Use case for "loop: Issue O_DIRECT aio with pages"? Date: Thu, 1 Mar 2012 18:15:24 -0500 Message-ID: <20120301231524.GG32588@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Dave Kleikamp , linux-fsdevel@vger.kernel.org To: Zach Brown Return-path: Received: from li9-11.members.linode.com ([67.18.176.11]:51719 "EHLO test.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754481Ab2CAXP2 (ORCPT ); Thu, 1 Mar 2012 18:15:28 -0500 Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-ID: > >My latest focus is on completing the work started on by Zach Brown to > >add a kernel interface to allow kernel code to submit aio, and having > >the loop device submit direct IO requests to the underlying file system. So I've been taking a lot at your patch series, and one of the things which would help me understand the requirements behind what you are doing is *why* is it interesting to allow kernel code to submit aio requests, and loop devices to be able to direct I/O requests all the way to the underlying file systems. In other words, what's the use case that you're most interested in that these patches would enable? Thanks, regards, - Ted