public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: fdmanana@kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: reduce size and overhead of extent_map_block_end()
Date: Wed, 24 Jul 2024 07:22:19 +0930	[thread overview]
Message-ID: <685fcf3b-012d-427f-968d-ccd5517a398a@gmx.com> (raw)
In-Reply-To: <9003408d1f29de77deef59c6ed6e5bf1d98b91ab.1721746528.git.fdmanana@suse.com>



在 2024/7/24 00:46, fdmanana@kernel.org 写道:
> From: Filipe Manana <fdmanana@suse.com>
>
> At extent_map_block_end() we are calling the inline functions
> extent_map_block_start() and extent_map_block_len() multiple times, which
> results in expanding their code multiple times, increasing the compiled
> code size and repeating the computations those functions do.
>
> Improve this by caching their results in local variables.
>
> The size of the module before this change:
>
>     $ size fs/btrfs/btrfs.ko
>        text	   data	    bss	    dec	    hex	filename
>     1755770	 163800	  16920	1936490	 1d8c6a	fs/btrfs/btrfs.ko
>
> And after this change:
>
>     $ size fs/btrfs/btrfs.ko
>        text	   data	    bss	    dec	    hex	filename
>     1755656	 163800	  16920	1936376	 1d8bf8	fs/btrfs/btrfs.ko
>
> Signed-off-by: Filipe Manana <fdmanana@suse.com>

Reviewed-by: Qu Wenruo <wqu@suse.com>

Thanks,
Qu

> ---
>   fs/btrfs/extent_map.c | 9 ++++++---
>   1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/fs/btrfs/extent_map.c b/fs/btrfs/extent_map.c
> index f85f0172b58b..806a8954b3d5 100644
> --- a/fs/btrfs/extent_map.c
> +++ b/fs/btrfs/extent_map.c
> @@ -192,10 +192,13 @@ static inline u64 extent_map_block_len(const struct extent_map *em)
>
>   static inline u64 extent_map_block_end(const struct extent_map *em)
>   {
> -	if (extent_map_block_start(em) + extent_map_block_len(em) <
> -	    extent_map_block_start(em))
> +	const u64 block_start = extent_map_block_start(em);
> +	const u64 block_end = block_start + extent_map_block_len(em);
> +
> +	if (block_end < block_start)
>   		return (u64)-1;
> -	return extent_map_block_start(em) + extent_map_block_len(em);
> +
> +	return block_end;
>   }
>
>   static bool can_merge_extent_map(const struct extent_map *em)

      parent reply	other threads:[~2024-07-23 21:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-23 15:16 [PATCH] btrfs: reduce size and overhead of extent_map_block_end() fdmanana
2024-07-23 15:40 ` Josef Bacik
2024-07-23 21:52 ` Qu Wenruo [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=685fcf3b-012d-427f-968d-ccd5517a398a@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=fdmanana@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox