From: tristan <tristan.ye@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/2] Ocfs2: Optimize truncting codes for ocfs2 to use ocfs2_remove_btree_range instead.
Date: Tue, 09 Feb 2010 09:12:07 +0800 [thread overview]
Message-ID: <4B70B667.6070103@oracle.com> (raw)
In-Reply-To: <20100209004756.GF1832@mail.oracle.com>
Joel Becker wrote:
> On Fri, Feb 05, 2010 at 06:45:31PM +0800, Tristan Ye wrote:
>
>> I merge the following steps into one patch since they may be logically doing one thing,
>> Though I knew it looks a little bit fat to review.
>>
>> 1). Remove redundant codes used by ocfs2_commit_truncate before, since we're moving to
>> ocfs2_remove_btree_range anyway.
>>
>> 2). Add a new func ocfs2_reserve_blocks_for_rec_trunc() for purpose of accepting some
>> extra blocks to reserve.
>>
>> 3). Change ocfs2_prepare_refcount_change_for_del() a bit to fit our needs, it's safe to
>> do this since it's only being called by truncating codes.
>>
>> 4). Change ocfs2_remove_btree_range() a bit to take refcount case into account.
>>
>> 5). Finally, we change ocfs2_commit_truncate() to call ocfs2_remove_btree_range() in
>> a proper way.
>>
>
> I was going to be mad that these 5 things weren't five patches,
> but actually it reads pretty well as a patch. I'm OK with it being one
> patch.
>
Joel,
Yes, it actually was doing one thing logically, the reason why I listed
the steps is try to make things straightforward.
To separate the patch into five smaller ones was really a bad idea,
which turns the code into a inconsistent state after applying each.
Thanks,
Tristan.
> Mark, can I get an Ack?
>
> Joel
>
>
next prev parent reply other threads:[~2010-02-09 1:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 10:45 [Ocfs2-devel] [PATCH 1/2] Ocfs2: Optimize truncting codes for ocfs2 to use ocfs2_remove_btree_range instead Tristan Ye
2010-02-05 10:45 ` [Ocfs2-devel] [PATCH 2/2] Ocfs2: Fix punching hole codes to correctly do CoW during cluster zeroing Tristan Ye
2010-02-06 0:32 ` Tao Ma
2010-02-09 0:50 ` Joel Becker
2010-02-06 0:32 ` [Ocfs2-devel] [PATCH 1/2] Ocfs2: Optimize truncting codes for ocfs2 to use ocfs2_remove_btree_range instead Tao Ma
2010-02-08 2:12 ` tristan
2010-02-09 0:47 ` Joel Becker
2010-02-09 1:12 ` tristan [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-08 10:51 Tristan Ye
2010-02-01 10:29 Tristan Ye
2010-02-01 22:20 ` TaoMa
2010-02-02 1:32 ` tristan
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=4B70B667.6070103@oracle.com \
--to=tristan.ye@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 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.