From: Thomas Hellstrom <thellstrom@vmware.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
Dave Airlie <airlied@redhat.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kref: prefer atomic_inc_not_zero to atomic_add_unless
Date: Sun, 11 Oct 2015 21:59:34 +0200 [thread overview]
Message-ID: <561ABFA6.8050102@vmware.com> (raw)
In-Reply-To: <1444474594-28359-1-git-send-email-Jason@zx2c4.com>
Reviewed-by: Thomas Hellstrom <thellstrom@vmware.com>
On 10/10/2015 12:56 PM, Jason A. Donenfeld wrote:
> On most platforms, there exists this ifdef:
>
> #define atomic_inc_not_zero(v) atomic_add_unless((v), 1, 0)
>
> This makes this patch functionally useless. However, on PPC, there is
> actually an explicit definition of atomic_inc_not_zero with its own
> assembly that is slightly more optimized than atomic_add_unless. So,
> this patch changes kref to use atomic_inc_not_zero instead, for PPC and
> any future platforms that might provide an explicit implementation.
>
> This also puts this usage of kref more in line with a verbatim reading
> of the examples in Paul McKenney's paper [1] in the section titled "2.4
> Atomic Counting With Check and Release Memory Barrier", which uses
> atomic_inc_not_zero.
>
> [1] https://urldefense.proofpoint.com/v2/url?u=http-3A__open-2Dstd.org_jtc1_sc22_wg21_docs_papers_2007_n2167.pdf&d=BQIBAg&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=vpukPkBtpoNQp2IUKuFviOmPNYWVKmen3Jeeu55zmEA&m=z5Nd9sYiJMKiphNjyZp6XT5CbayXMBlcb903f260pDY&s=HEHX3CuXRs2GRRQWuC4Vef6iJMwdilKVRkiZgJpjEpA&e=
>
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> ---
> include/linux/kref.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/kref.h b/include/linux/kref.h
> index 484604d..83d1f94 100644
> --- a/include/linux/kref.h
> +++ b/include/linux/kref.h
> @@ -166,6 +166,6 @@ static inline int kref_put_mutex(struct kref *kref,
> */
> static inline int __must_check kref_get_unless_zero(struct kref *kref)
> {
> - return atomic_add_unless(&kref->refcount, 1, 0);
> + return atomic_inc_not_zero(&kref->refcount);
> }
> #endif /* _KREF_H_ */
next prev parent reply other threads:[~2015-10-11 19:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-10 10:56 [PATCH] kref: prefer atomic_inc_not_zero to atomic_add_unless Jason A. Donenfeld
2015-10-11 19:59 ` Thomas Hellstrom [this message]
2016-02-01 21:53 ` Jason A. Donenfeld
2016-06-29 22:52 ` Jason A. Donenfeld
2016-07-01 7:08 ` Patch for drm-next WAS " Thomas Hellstrom
2016-07-12 12:28 ` Daniel Vetter
2016-12-15 4:59 ` Jason A. Donenfeld
2016-12-15 4:58 ` Jason A. Donenfeld
2016-12-15 8:51 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2016-12-15 18:55 Jason A. Donenfeld
2016-12-15 19:10 ` Greg KH
2016-12-15 19:47 ` Jason A. Donenfeld
2016-12-16 7:36 ` Daniel Vetter
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=561ABFA6.8050102@vmware.com \
--to=thellstrom@vmware.com \
--cc=Jason@zx2c4.com \
--cc=airlied@redhat.com \
--cc=linux-kernel@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