From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Theodore Tso <tytso@mit.edu>
Cc: cmm@us.ibm.com, sandeen@redhat.com, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: Use an rb tree for tracking blocks freed during transaction.
Date: Sat, 11 Oct 2008 23:38:00 +0530 [thread overview]
Message-ID: <20081011180800.GA9662@skywalker> (raw)
In-Reply-To: <20081011042738.GC8145@mit.edu>
On Sat, Oct 11, 2008 at 12:27:38AM -0400, Theodore Tso wrote:
> On Thu, Oct 09, 2008 at 09:02:07PM +0530, Aneesh Kumar K.V wrote:
> > With this patch we track the block freed during a transaction using
> > rb tree. We also make sure contiguos blocks freed are collected
> > in one rb node.
>
> Thanks, I've added your recent set of patches to the ext4 patch queue.
> I'm pretty sure I grabbed the correct (most recent) patches from the
> mailing list, but please double check for me.
>
I verified the patch queue. It looks fine. I also tested the latest
patchqueue (I commented out the defrag patch because they were giving
error during apply) on ABAT and all the tests PASSED.
-aneesh
next prev parent reply other threads:[~2008-10-11 18:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 15:32 [PATCH] ext4: Use an rb tree for tracking blocks freed during transaction Aneesh Kumar K.V
2008-10-09 15:32 ` [PATCH] ext4: Don't reuse released data blocks untill transaction commits Aneesh Kumar K.V
2008-10-09 15:32 ` [PATCH] ext4: Do mballoc init before doing filesystem recovery Aneesh Kumar K.V
2008-10-12 20:33 ` [PATCH] ext4: Don't reuse released data blocks untill transaction commits Theodore Tso
2008-10-11 4:27 ` [PATCH] ext4: Use an rb tree for tracking blocks freed during transaction Theodore Tso
2008-10-11 18:08 ` Aneesh Kumar K.V [this message]
2008-10-12 20:31 ` Theodore Tso
2008-10-13 9:46 ` Aneesh Kumar K.V
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=20081011180800.GA9662@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--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.