From: Michael Rubin <mrubin@google.com>
To: Valerie Aurora <vaurora@redhat.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
Jiaying Zhang <jiayingz@google.com>,
tytso@mit.edu, Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH v4 0/3] dioread_nolock patch
Date: Fri, 19 Feb 2010 16:56:39 -0800 [thread overview]
Message-ID: <532480951002191656m17ce0880n75cedd0534689365@mail.gmail.com> (raw)
In-Reply-To: <20100122204715.GA6781@shell>
On Fri, Jan 22, 2010 at 12:47 PM, Valerie Aurora <vaurora@redhat.com> wrote:
> Don't let the perfect be the enemy of the good. :) I'd love to see
> what you've got now, even if you have to leave out the closed part of it.
>
We are currently reviewing a paper to send out this data.
Sorry to take so long but we have been very busy with the ext4 upgrade.
We plan on publishing other papers about our experiences with ext4
this summer also.
Out of curiosity is there anything anyone is curious about in the file
system space?
mrubin
next prev parent reply other threads:[~2010-02-20 0:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 19:30 [PATCH v4 0/3] dioread_nolock patch Theodore Ts'o
2010-01-15 19:30 ` [PATCH v4 1/3] ext4: mechanical change on dio get_block code in prepare for it to be used by buffer write Theodore Ts'o
2010-01-17 14:36 ` Aneesh Kumar K. V
2010-01-17 16:19 ` Eric Sandeen
2010-01-17 16:42 ` Aneesh Kumar K. V
2010-01-18 3:57 ` tytso
2010-01-15 19:30 ` [PATCH v4 2/3] ext4: use ext4_get_block_write in " Theodore Ts'o
2010-01-16 2:17 ` tytso
2010-01-17 14:21 ` Aneesh Kumar K. V
2010-01-18 5:25 ` Jiaying Zhang
2010-01-15 19:30 ` [PATCH v4 3/3] ext4: Use direct_IO_no_locking in ext4 dio read Theodore Ts'o
2010-01-17 14:19 ` Aneesh Kumar K. V
2010-01-15 19:39 ` [PATCH v4 0/3] dioread_nolock patch Ric Wheeler
2010-01-15 19:52 ` Eric Sandeen
2010-01-15 20:15 ` tytso
2010-01-15 20:17 ` Eric Sandeen
2010-01-15 21:47 ` Michael Rubin
2010-01-22 20:47 ` Valerie Aurora
2010-02-20 0:56 ` Michael Rubin [this message]
2010-02-23 0:36 ` Andreas Dilger
2010-02-16 21:07 ` Darrick J. Wong
2010-02-17 19:34 ` Jiaying Zhang
2010-02-19 21:25 ` Darrick J. Wong
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=532480951002191656m17ce0880n75cedd0534689365@mail.gmail.com \
--to=mrubin@google.com \
--cc=jiayingz@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
--cc=vaurora@redhat.com \
/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).