From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Eric Dumazet <eric.dumazet@gmail.com>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, Kevin Hao <haokexin@gmail.com>,
Torsten Duwe <duwe@suse.de>, Eric Dumazet <edumazet@google.com>,
Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>
Subject: Re: [RFC] implement QUEUED spinlocks on powerpc
Date: Thu, 02 Feb 2017 07:37:25 +1100 [thread overview]
Message-ID: <1485981445.4850.8.camel@kernel.crashing.org> (raw)
In-Reply-To: <1485968734.6360.154.camel@edumazet-glaptop3.roam.corp.google.com>
On Wed, 2017-02-01 at 09:05 -0800, Eric Dumazet wrote:
> Hi all
>
> Is anybody working on adding QUEUED spinlocks to powerpc 64bit ?
>
> I've seen past attempts with ticket spinlocks
> ( https://patchwork.ozlabs.org/patch/449381/ and other related links
> )
>
> But it looks ticket spinlocks are a thing of the past.
Yes, we have a tentative implementation of qspinlock and pv variants:
https://patchwork.ozlabs.org/patch/703139/
https://patchwork.ozlabs.org/patch/703140/
https://patchwork.ozlabs.org/patch/703141/
https://patchwork.ozlabs.org/patch/703142/
https://patchwork.ozlabs.org/patch/703143/
https://patchwork.ozlabs.org/patch/703144/
Michael, what's the status with getting that merged ?
Cheers,
Ben.
next prev parent reply other threads:[~2017-02-01 20:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 17:05 [RFC] implement QUEUED spinlocks on powerpc Eric Dumazet
2017-02-01 20:37 ` Benjamin Herrenschmidt [this message]
2017-02-02 4:04 ` Michael Ellerman
2017-02-02 4:40 ` Eric Dumazet
2017-02-02 4:42 ` Benjamin Herrenschmidt
2017-02-07 6:21 ` panxinhui
2017-02-07 6:46 ` Eric Dumazet
2017-02-07 7:22 ` panxinhui
2017-02-13 9:08 ` panxinhui
2017-02-15 10:17 ` panxinhui
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=1485981445.4850.8.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=duwe@suse.de \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=haokexin@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=xinhui.pan@linux.vnet.ibm.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.