From: Ted Ts'o <tytso@mit.edu>
To: Zach Brown <zab@zabbo.net>
Cc: Dave Kleikamp <dave.kleikamp@oracle.com>, linux-fsdevel@vger.kernel.org
Subject: Use case for "loop: Issue O_DIRECT aio with pages"?
Date: Thu, 1 Mar 2012 18:15:24 -0500 [thread overview]
Message-ID: <20120301231524.GG32588@thunk.org> (raw)
> >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
next reply other threads:[~2012-03-01 23:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 23:15 Ted Ts'o [this message]
2012-03-02 2:49 ` Use case for "loop: Issue O_DIRECT aio with pages"? Zach Brown
2012-03-02 8:14 ` Ted Ts'o
2012-03-02 14:52 ` Zach Brown
2012-03-02 7:29 ` Christoph Hellwig
2012-03-02 14:14 ` Chris Mason
2012-03-02 20:50 ` James Bottomley
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=20120301231524.GG32588@thunk.org \
--to=tytso@mit.edu \
--cc=dave.kleikamp@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=zab@zabbo.net \
/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).