From: Ted Ts'o <tytso@mit.edu>
To: Dave Kleikamp <dave.kleikamp@oracle.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org
Subject: Re: [ATTEND] Attendance request
Date: Thu, 2 Feb 2012 15:29:11 -0500 [thread overview]
Message-ID: <20120202202911.GC1032@thunk.org> (raw)
In-Reply-To: <4F2ABF08.60502@oracle.com>
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
next prev parent reply other threads:[~2012-02-02 20:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 16:51 [ATTEND] Attendance request Dave Kleikamp
2012-02-02 19:00 ` Zach Brown
2012-02-02 19:07 ` Dave Kleikamp
2012-02-02 20:29 ` Ted Ts'o [this message]
2012-02-02 20:51 ` Zach Brown
2012-02-02 20:58 ` Ted Ts'o
2012-02-02 21:03 ` Zach Brown
2012-02-03 2:20 ` Zheng Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120202202911.GC1032@thunk.org \
--to=tytso@mit.edu \
--cc=dave.kleikamp@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).