From: Daniel Vetter <daniel@ffwll.ch>
To: Thomas Hellstrom <thellstrom@vmware.com>
Cc: Dave Airlie <airlied@redhat.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: Patch for drm-next WAS Re: [PATCH] kref: prefer atomic_inc_not_zero to atomic_add_unless
Date: Tue, 12 Jul 2016 14:28:17 +0200 [thread overview]
Message-ID: <20160712122817.GT23520@phenom.ffwll.local> (raw)
In-Reply-To: <842a1a37-7c57-ed57-7a80-97fb8a3c3f88@vmware.com>
On Fri, Jul 01, 2016 at 09:08:34AM +0200, Thomas Hellstrom wrote:
> Dave,
>
> Since kref_get_unless_zero() was brought in by drm, could we add this to
> drm-next?
Sure can do, but I can't find the raw patch anywhere (I suck, I know).
Care to resend?
Thanks, Daniel
>
> Thanks,
> Thomas
>
>
> On 06/30/2016 12:52 AM, Jason A. Donenfeld wrote:
> > This was positively reviewed by maintainers but never picked up. Can
> > someone queue this for 4.7 or 4.8?
> >
> > Thanks,
> > Jason
> >
> > On Mon, Feb 1, 2016 at 10:53 PM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> >> This was positively reviewed but never picked up. Can someone queue
> >> this for rc3?
> >>
> >> Thanks,
> >> Jason
> >>
> >> On Sun, Oct 11, 2015 at 9:59 PM, Thomas Hellstrom <thellstrom@vmware.com> wrote:
> >>> 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_ */
>
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-07-12 12:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1444474594-28359-1-git-send-email-Jason@zx2c4.com>
[not found] ` <561ABFA6.8050102@vmware.com>
[not found] ` <CAHmME9qZwkUqYxsTohUoNTLzxcPsrxV9swM3HH0rxpOLMmCmjQ@mail.gmail.com>
[not found] ` <CAHmME9rVPQ+SWqAe6Lqj4Do16mpCmSUz5_6Q2qyYj6mqnJec7g@mail.gmail.com>
2016-07-01 7:08 ` Patch for drm-next WAS Re: [PATCH] kref: prefer atomic_inc_not_zero to atomic_add_unless Thomas Hellstrom
2016-07-12 12:28 ` Daniel Vetter [this message]
2016-12-15 4:59 ` Jason A. Donenfeld
2016-12-15 5:01 ` Jason A. Donenfeld
2016-12-16 7:33 ` Daniel Vetter
2016-08-10 12:24 ` Fwd: " Thomas Hellstrom
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=20160712122817.GT23520@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=Jason@zx2c4.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=thellstrom@vmware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox