linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Goldwyn Rodrigues <rgoldwyn@suse.de>
Cc: linux-btrfs@vger.kernel.org, Goldwyn Rodrigues <rgoldwyn@suse.com>
Subject: Re: [PATCH] btrfs: cleanup extent locking sequence
Date: Fri, 13 Oct 2017 15:23:21 +0200	[thread overview]
Message-ID: <20171013132321.GN3521@twin.jikos.cz> (raw)
In-Reply-To: <20171011022641.21202-1-rgoldwyn@suse.de>

On Tue, Oct 10, 2017 at 09:26:41PM -0500, Goldwyn Rodrigues wrote:
> From: Goldwyn Rodrigues <rgoldwyn@suse.com>
> 
> Code cleanup for better understanding:
> needs_unlock to be called extent_locked to show state as opposed to
> action.
> Changed the variable to int, to reduce code in the critical path(code usually
> executed).
> 
> Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>
> ---
>  fs/btrfs/file.c | 14 ++++++--------
>  1 file changed, 6 insertions(+), 8 deletions(-)
> 
> diff --git a/fs/btrfs/file.c b/fs/btrfs/file.c
> index f6c6754cf52d..a3d006d14683 100644
> --- a/fs/btrfs/file.c
> +++ b/fs/btrfs/file.c
> @@ -1590,7 +1590,7 @@ static noinline ssize_t __btrfs_buffered_write(struct file *file,
>  	int ret = 0;
>  	bool only_release_metadata = false;
>  	bool force_page_uptodate = false;
> -	bool need_unlock;
> +	int extents_locked;

The variable can be moved to the while() { } block

>  
>  	nrptrs = min(DIV_ROUND_UP(iov_iter_count(i), PAGE_SIZE),
>  			PAGE_SIZE / (sizeof(struct page *)));
> @@ -1670,7 +1670,6 @@ static noinline ssize_t __btrfs_buffered_write(struct file *file,
>  		}
>  
>  		release_bytes = reserve_bytes;
> -		need_unlock = false;
>  again:
>  		/*
>  		 * This is going to setup the pages array with the number of
> @@ -1683,16 +1682,15 @@ static noinline ssize_t __btrfs_buffered_write(struct file *file,
>  		if (ret)
>  			break;
>  
> -		ret = lock_and_cleanup_extent_if_need(BTRFS_I(inode), pages,
> +		extents_locked = lock_and_cleanup_extent_if_need(
> +				BTRFS_I(inode), pages,
>  				num_pages, pos, write_bytes, &lockstart,
>  				&lockend, &cached_state);
> -		if (ret < 0) {
> +		if (extents_locked < 0) {
>  			if (ret == -EAGAIN)

either

		if (extents_locked == -EAGAIN)

or

		move 'ret = extents_locked' above the if.

>  				goto again;
> +			ret = extents_locked;
>  			break;
> -		} else if (ret > 0) {
> -			need_unlock = true;
> -			ret = 0;
>  		}

      reply	other threads:[~2017-10-13 13:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11  2:26 [PATCH] btrfs: cleanup extent locking sequence Goldwyn Rodrigues
2017-10-13 13:23 ` 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=20171013132321.GN3521@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --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).