From: David Sterba <dsterba@suse.cz>
To: Nikolay Borisov <nborisov@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: remove redundant local var in read_block_for_search
Date: Wed, 27 May 2020 16:02:17 +0200 [thread overview]
Message-ID: <20200527140217.GH18421@twin.jikos.cz> (raw)
In-Reply-To: <20200527101059.7391-1-nborisov@suse.com>
On Wed, May 27, 2020 at 01:10:59PM +0300, Nikolay Borisov wrote:
> The local 'b' variable is only used to directly read values from passed
> extent buffer. So eliminate it and directly use the input parameter. Furthermore
> this shrinks the size of the following functions:
>
> ./scripts/bloat-o-meter ctree.orig fs/btrfs/ctree.o
> add/remove: 0/0 grow/shrink: 0/2 up/down: 0/-73 (-73)
> Function old new delta
> read_block_for_search.isra 876 871 -5
> push_node_left 1112 1044 -68
> - struct extent_buffer *b = *eb_ret;
> - blocknr = btrfs_node_blockptr(b, slot);
> - gen = btrfs_node_ptr_generation(b, slot);
> - parent_level = btrfs_header_level(b);
> - btrfs_node_key_to_cpu(b, &first_key, slot);
> + blocknr = btrfs_node_blockptr(*eb_ret, slot);
> + gen = btrfs_node_ptr_generation(*eb_ret, slot);
> + parent_level = btrfs_header_level(*eb_ret);
> + btrfs_node_key_to_cpu(*eb_ret, &first_key, slot);
It's interesting how such trivial and obvious change can improve the
code generation. The removed indirection resulted in smaller function
push_node_left that is not even called directly, but as there are lot of
static helpers it's some intra-procedural pass that can utilize the
reduced variable indirection.
prev parent reply other threads:[~2020-05-27 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 10:10 [PATCH] btrfs: remove redundant local var in read_block_for_search Nikolay Borisov
2020-05-27 11:57 ` Johannes Thumshirn
2020-05-27 13:56 ` David Sterba
2020-05-27 14:02 ` David Sterba [this message]
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=20200527140217.GH18421@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.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).