From: Theodore Ts'o <tytso@mit.edu>
To: Zach Brown <zab@redhat.com>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>,
Zheng Liu <gnehzuil.liu@gmail.com>,
Zheng Liu <wenqing.lz@taobao.com>
Subject: Re: [RFC PATCH 3/3] ext4: cache all of an extent tree's leaf block upon reading
Date: Thu, 11 Jul 2013 15:33:56 -0400 [thread overview]
Message-ID: <20130711193356.GB11689@thunk.org> (raw)
In-Reply-To: <20130711185423.GA25414@lenny.home.zabbo.net>
On Thu, Jul 11, 2013 at 11:54:23AM -0700, Zach Brown wrote:
>
> Isn't prev going to be reinitialized to 0 for every extent?
Whoops, nice catch. I'll fix this in my next spin of the patches.
- Ted
next prev parent reply other threads:[~2013-07-11 19:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 4:39 [RFC PATCH 1/3] ext4: refactor code to read the extent tree block Theodore Ts'o
2013-07-11 4:39 ` [RFC PATCH 2/3] ext4: use unsigned int for es_status values Theodore Ts'o
2013-07-11 12:48 ` Zheng Liu
2013-07-11 4:39 ` [RFC PATCH 3/3] ext4: cache all of an extent tree's leaf block upon reading Theodore Ts'o
2013-07-11 12:52 ` Zheng Liu
2013-07-11 18:54 ` Zach Brown
2013-07-11 19:33 ` Theodore Ts'o [this message]
2013-07-11 12:41 ` [RFC PATCH 1/3] ext4: refactor code to read the extent tree block 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=20130711193356.GB11689@thunk.org \
--to=tytso@mit.edu \
--cc=gnehzuil.liu@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=wenqing.lz@taobao.com \
--cc=zab@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).