From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ted Ts'o Subject: Re: [ATTEND] Attendance request Date: Thu, 2 Feb 2012 15:29:11 -0500 Message-ID: <20120202202911.GC1032@thunk.org> References: <4F2ABF08.60502@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org To: Dave Kleikamp Return-path: Received: from li9-11.members.linode.com ([67.18.176.11]:42309 "EHLO test.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752846Ab2BBU3O (ORCPT ); Thu, 2 Feb 2012 15:29:14 -0500 Content-Disposition: inline In-Reply-To: <4F2ABF08.60502@oracle.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Feb 02, 2012 at 10:51:20AM -0600, Dave Kleikamp wrote: > Committee members, > > Please consider inviting me to the Storage, Filesystem, & MM Summit. I > am working in Chris Mason's team at Oracle focusing on storage I/O. > > 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. We should talk; I'm currently working on an async bmap function for ext4, which I then intended to use for a modified high-level AIO support framework that allowed for async metadata access. That is, I'm interested in solving the "AIO isn't really 'A'" problem. That's a different problem that what you're working on, but it's obviously going to touch the same code. (Actually, my original plan was to not touch the generic code in __blockdev_direct_IO and below and create some ext4-specific code for now, but if you're going to be messing around in that code path anyway, we should coordinate....) - Ted