linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: Goldwyn Rodrigues <rgoldwyn@suse.de>, linux-btrfs@vger.kernel.org
Cc: Goldwyn Rodrigues <rgoldwyn@suse.com>
Subject: Re: [PATCH] btrfs: Simplify update space_info in __reserve_metadata_bytes()
Date: Wed, 19 Jun 2019 17:15:44 +0300	[thread overview]
Message-ID: <a59c0738-9f6e-f18f-fa64-4d185bc07057@suse.com> (raw)
In-Reply-To: <20190619141249.23001-1-rgoldwyn@suse.de>



On 19.06.19 г. 17:12 ч., Goldwyn Rodrigues wrote:
> From: Goldwyn Rodrigues <rgoldwyn@suse.com>
> 
> Simplification.
> We don't need an if-else-if structure where we can use a
> simple OR since both conditions are performing the
> same action. The short-circuit for OR will ensure that if
> the first condition is true, can_overcommit() is not
> called.
> 
> Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>

Reviewed-by: Nikolay Borisov <nborisov@suse.com>

> ---
>  fs/btrfs/extent-tree.c | 14 +++++---------
>  1 file changed, 5 insertions(+), 9 deletions(-)
> 
> diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
> index c7adff343ba9..84a33cbb1e68 100644
> --- a/fs/btrfs/extent-tree.c
> +++ b/fs/btrfs/extent-tree.c
> @@ -5158,17 +5158,13 @@ static int __reserve_metadata_bytes(struct btrfs_fs_info *fs_info,
>  	used = btrfs_space_info_used(space_info, true);
>  
>  	/*
> -	 * If we have enough space then hooray, make our reservation and carry
> -	 * on.  If not see if we can overcommit, and if we can, hooray carry on.
> +	 * Carry on if we have enough space (short-circuit) OR call
> +	 * can_overcommit() to ensure we can overcommit to carry on.
>  	 * If not things get more complicated.
>  	 */
> -	if (used + orig_bytes <= space_info->total_bytes) {
> -		update_bytes_may_use(space_info, orig_bytes);
> -		trace_btrfs_space_reservation(fs_info, "space_info",
> -					      space_info->flags, orig_bytes, 1);
> -		ret = 0;
> -	} else if (can_overcommit(fs_info, space_info, orig_bytes, flush,
> -				  system_chunk)) {
> +	if ((used + orig_bytes <= space_info->total_bytes) ||
> +	    can_overcommit(fs_info, space_info, orig_bytes, flush,
> +			    system_chunk)) {
>  		update_bytes_may_use(space_info, orig_bytes);
>  		trace_btrfs_space_reservation(fs_info, "space_info",
>  					      space_info->flags, orig_bytes, 1);
> 

  reply	other threads:[~2019-06-19 14:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-19 14:12 [PATCH] btrfs: Simplify update space_info in __reserve_metadata_bytes() Goldwyn Rodrigues
2019-06-19 14:15 ` Nikolay Borisov [this message]
2019-06-25 18:13 ` 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=a59c0738-9f6e-f18f-fa64-4d185bc07057@suse.com \
    --to=nborisov@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rgoldwyn@suse.com \
    --cc=rgoldwyn@suse.de \
    /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).