From: Zach Brown <zab@zabbo.net>
To: Ted Ts'o <tytso@mit.edu>
Cc: Dave Kleikamp <dave.kleikamp@oracle.com>, linux-fsdevel@vger.kernel.org
Subject: Re: [ATTEND] Attendance request
Date: Thu, 02 Feb 2012 15:51:03 -0500 [thread overview]
Message-ID: <4F2AF737.9020106@zabbo.net> (raw)
In-Reply-To: <20120202202911.GC1032@thunk.org>
> 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.
Well, for that one blocking case in the submission path.
I certainly understand the desire to just make things less painful in
this case, but I do wonder if the long-term win is to sink resources
into trying to get threads executings async op so that the code paths
don't have to be butchered into state machines around each potential
blocking op.
It's a lot of work to get it transparent and efficient, I know. But
then we'd be out of the business of obfuscating our code paths.
- z
next prev parent reply other threads:[~2012-02-02 20:51 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
2012-02-02 20:51 ` Zach Brown [this message]
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=4F2AF737.9020106@zabbo.net \
--to=zab@zabbo.net \
--cc=dave.kleikamp@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.