All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: Rashika Kheria <rashika.kheria@gmail.com>
Cc: opw-kernel@googlegroups.com, linux-btrfs@vger.kernel.org
Subject: Re: [OPW kernel] [PATCH v2] btrfs: Replace multiple atomic_inc() with atomic_add()
Date: Sat, 2 Nov 2013 09:59:32 -0700	[thread overview]
Message-ID: <20131102165932.GI15704@leaf> (raw)
In-Reply-To: <1383169362-25993-1-git-send-email-rashika.kheria@gmail.com>

On Thu, Oct 31, 2013 at 03:12:42AM +0530, Rashika Kheria wrote:
> This patch replaces multiple atomic_inc() with atomic_add() in
> delayed-inode.c to reduce source code and have few instructions
> for compilation.
> 
> Reviewed-by: Zach Brown <zab@redhat.com>
> Signed-off-by: Rashika Kheria <rashika.kheria@gmail.com>

Reviewed-by: Josh Triplett <josh@joshtriplett.org>

> 
> This revision fixes the following issues of the previous revision-
> Space in comment
> 
>  fs/btrfs/delayed-inode.c |    8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/fs/btrfs/delayed-inode.c b/fs/btrfs/delayed-inode.c
> index cbd9523..504a9b5 100644
> --- a/fs/btrfs/delayed-inode.c
> +++ b/fs/btrfs/delayed-inode.c
> @@ -108,8 +108,8 @@ static struct btrfs_delayed_node *btrfs_get_delayed_node(struct inode *inode)
>  			return node;
>  		}
>  		btrfs_inode->delayed_node = node;
> -		atomic_inc(&node->refs);	/* can be accessed */
> -		atomic_inc(&node->refs);	/* cached in the inode */
> +		/* can be accessed and cached in the inode */
> +		atomic_add(2, &node->refs);
>  		spin_unlock(&root->inode_lock);
>  		return node;
>  	}
> @@ -138,8 +138,8 @@ again:
>  		return ERR_PTR(-ENOMEM);
>  	btrfs_init_delayed_node(node, root, ino);
>  
> -	atomic_inc(&node->refs);	/* cached in the btrfs inode */
> -	atomic_inc(&node->refs);	/* can be accessed */
> +	/* cached in the btrfs inode and can be accessed */
> +	atomic_add(2, &node->refs);
>  
>  	ret = radix_tree_preload(GFP_NOFS & ~__GFP_HIGHMEM);
>  	if (ret) {
> -- 
> 1.7.9.5
> 
> -- 
> You received this message because you are subscribed to the Google Groups "opw-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to opw-kernel+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

      reply	other threads:[~2013-11-02 16:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20131030212314.GA25069@gmail.com>
2013-10-30 21:42 ` [PATCH v2] btrfs: Replace multiple atomic_inc() with atomic_add() Rashika Kheria
2013-11-02 16:59   ` Josh Triplett [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=20131102165932.GI15704@leaf \
    --to=josh@joshtriplett.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=opw-kernel@googlegroups.com \
    --cc=rashika.kheria@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.