From: David Sterba <dsterba@suse.cz>
To: Alexandru Moise <00moses.alexander00@gmail.com>
Cc: clm@fb.com, jbacik@fb.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] btrfs: memset cur_trans->delayed_refs to zero
Date: Mon, 7 Sep 2015 14:24:20 +0200 [thread overview]
Message-ID: <20150907122419.GT11834@suse.cz> (raw)
In-Reply-To: <20150906122527.GA21685@gmail.com>
On Sun, Sep 06, 2015 at 12:25:27PM +0000, Alexandru Moise wrote:
> Use memset() to null out the btrfs_delayed_ref_root of
> btrfs_transaction instead of setting all the members to 0 by hand.
>
> Signed-off-by: Alexandru Moise <00moses.alexander00@gmail.com>
> ---
> fs/btrfs/transaction.c | 10 +---------
> 1 file changed, 1 insertion(+), 9 deletions(-)
>
> diff --git a/fs/btrfs/transaction.c b/fs/btrfs/transaction.c
> index 8f259b3..faccc1b 100644
> --- a/fs/btrfs/transaction.c
> +++ b/fs/btrfs/transaction.c
> @@ -224,15 +224,7 @@ loop:
> cur_trans->start_time = get_seconds();
> cur_trans->dirty_bg_run = 0;
>
> - cur_trans->delayed_refs.href_root = RB_ROOT;
> - cur_trans->delayed_refs.dirty_extent_root = RB_ROOT;
> - atomic_set(&cur_trans->delayed_refs.num_entries, 0);
Please keep these. Even if it means duplicated setting to 0, it's using
the correct constructor, should it ever change (RB_ROOT) or does some
extra work (atomic_set).
next prev parent reply other threads:[~2015-09-07 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-06 12:25 [PATCH] btrfs: memset cur_trans->delayed_refs to zero Alexandru Moise
2015-09-07 12:24 ` David Sterba [this message]
2015-09-07 13:44 ` Alexandru Moise
-- strict thread matches above, loose matches on Subject: below --
2015-09-07 13:45 Alexandru Moise
2015-09-07 14:01 ` David Sterba
2015-09-07 14:23 ` Alexandru Moise
2015-09-07 14:24 Alexandru Moise
2015-09-22 13:04 ` David Sterba
2015-09-22 13:19 ` Alexandru Moise
2015-09-22 13:24 ` David Sterba
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=20150907122419.GT11834@suse.cz \
--to=dsterba@suse.cz \
--cc=00moses.alexander00@gmail.com \
--cc=clm@fb.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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 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).