From: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 5/6] Btrfs-progs: fsck: reduce memory usage of extent record struct
Date: Wed, 19 Mar 2014 09:11:55 +0800 [thread overview]
Message-ID: <5328EEDB.8000202@cn.fujitsu.com> (raw)
In-Reply-To: <20140318181854.GI29256@twin.jikos.cz>
On 03/19/2014 02:18 AM, David Sterba wrote:
> On Tue, Mar 18, 2014 at 08:02:46PM +0800, Wang Shilong wrote:
>> @@ -2742,7 +2742,10 @@ static int add_extent_rec(struct cache_tree *extent_cache,
>> - rec->found_rec = extent_rec;
>> + if (extent_rec)
>> + rec->found_rec = 1;
>> + else
>> + rec->found_rec = 0;
> I've modified this to avoid 'if'
>
> rec->found_rec = !!extent_rec;
Dave, thanks for doing this.:-)
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-03-19 1:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 12:02 [PATCH 1/6] Btrfs-progs: fsck: don't free @seen cache until we finish searching Wang Shilong
2014-03-18 12:02 ` [PATCH 2/6] Btrfs-progs: fsck: fix possible memory leaks in run_next_block() Wang Shilong
2014-03-18 12:02 ` [PATCH 3/6] Btrfs-progs: fsck: deal with snapshot one by one when rebuilding extent tree Wang Shilong
2014-03-18 12:02 ` [PATCH 4/6] Btrfs-progs: fsck: add ability to rebuild extent tree with snapshots Wang Shilong
2014-03-18 12:02 ` [PATCH 5/6] Btrfs-progs: fsck: reduce memory usage of extent record struct Wang Shilong
2014-03-18 18:18 ` David Sterba
2014-03-19 1:11 ` Wang Shilong [this message]
2014-03-18 12:02 ` [PATCH 6/6] Btrfs-progs: fsck: fix wrong index in pick_next_pending() Wang Shilong
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=5328EEDB.8000202@cn.fujitsu.com \
--to=wangsl.fnst@cn.fujitsu.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
/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.