From: Will Deacon <will.deacon@arm.com>
To: Yury Norov <ynorov@caviumnetworks.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
pan xinhui <mnipxh@hotmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Adam Wallis <awallis@codeaurora.org>,
Andrew Pinski <Andrew.Pinski@cavium.com>,
Arnd Bergmann <arnd@arndb.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Ingo Molnar <mingo@redhat.com>, Jan Glauber <jglauber@cavium.com>,
Mark Rutland <mark.rutland@arm.com>,
Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>
Subject: Re: 答复: [PATCH 0/3] arm64: queued spinlocks and rw-locks
Date: Fri, 5 May 2017 16:32:46 +0100 [thread overview]
Message-ID: <20170505153245.GH14111@arm.com> (raw)
In-Reply-To: <20170505152845.e32h3jxhjdjw6yht@yury-N73SV>
On Fri, May 05, 2017 at 06:28:45PM +0300, Yury Norov wrote:
> On Fri, May 05, 2017 at 01:26:40PM +0100, Will Deacon wrote:
> > On Fri, May 05, 2017 at 01:53:03PM +0200, Peter Zijlstra wrote:
> > > On Thu, May 04, 2017 at 11:28:09PM +0300, Yury Norov wrote:
> > > > I don't think
> > > > it's a real use case to have ticket spinlocks and queued rwlocks
> > >
> > > There's nothing wrong with that combination. In fact, we merged qrwlock
> > > much earlier than qspinlock.
> >
> > ... and that's almost certainly the direction we'll go on arm64 too, not
> > least because the former are a lot easier to grok.
> >
> > Will
>
> Hmm. Then I think I have to split patch 3 to rwlock and spinlock
> parts, and allow user to enable them independently in config.
To be honest, I'm going to spend some time looking at the qrwlock code again
before I enable it for arm64, so I don't think you need to rush to resend
patches since I suspect I'll have a few in the meantime.
Will
WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: 答复: [PATCH 0/3] arm64: queued spinlocks and rw-locks
Date: Fri, 5 May 2017 16:32:46 +0100 [thread overview]
Message-ID: <20170505153245.GH14111@arm.com> (raw)
In-Reply-To: <20170505152845.e32h3jxhjdjw6yht@yury-N73SV>
On Fri, May 05, 2017 at 06:28:45PM +0300, Yury Norov wrote:
> On Fri, May 05, 2017 at 01:26:40PM +0100, Will Deacon wrote:
> > On Fri, May 05, 2017 at 01:53:03PM +0200, Peter Zijlstra wrote:
> > > On Thu, May 04, 2017 at 11:28:09PM +0300, Yury Norov wrote:
> > > > I don't think
> > > > it's a real use case to have ticket spinlocks and queued rwlocks
> > >
> > > There's nothing wrong with that combination. In fact, we merged qrwlock
> > > much earlier than qspinlock.
> >
> > ... and that's almost certainly the direction we'll go on arm64 too, not
> > least because the former are a lot easier to grok.
> >
> > Will
>
> Hmm. Then I think I have to split patch 3 to rwlock and spinlock
> parts, and allow user to enable them independently in config.
To be honest, I'm going to spend some time looking at the qrwlock code again
before I enable it for arm64, so I don't think you need to rush to resend
patches since I suspect I'll have a few in the meantime.
Will
next prev parent reply other threads:[~2017-05-05 15:32 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 14:51 [PATCH 0/3] arm64: queued spinlocks and rw-locks Yury Norov
2017-05-03 14:51 ` Yury Norov
2017-05-03 14:51 ` [PATCH 1/3] kernel/locking: #include <asm/spinlock.h> in qrwlock.c Yury Norov
2017-05-03 14:51 ` Yury Norov
2017-05-03 15:05 ` Geert Uytterhoeven
2017-05-03 15:05 ` Geert Uytterhoeven
2017-05-03 15:05 ` Geert Uytterhoeven
2017-05-03 20:32 ` Yury Norov
2017-05-03 20:32 ` Yury Norov
2017-05-03 14:51 ` [PATCH 2/3] asm-generic: don't #include <linux/atomic.h> in qspinlock_types.h Yury Norov
2017-05-03 14:51 ` Yury Norov
2017-05-04 8:01 ` Arnd Bergmann
2017-05-04 8:01 ` Arnd Bergmann
2017-05-03 14:51 ` [PATCH 3/3] arm64/locking: qspinlocks and qrwlocks support Yury Norov
2017-05-03 14:51 ` Yury Norov
2017-05-09 4:47 ` Boqun Feng
2017-05-09 4:47 ` Boqun Feng
2017-05-09 18:48 ` Yury Norov
2017-05-09 18:48 ` Yury Norov
2017-05-09 19:37 ` Yury Norov
2017-05-09 19:37 ` Yury Norov
2017-05-03 18:59 ` 答复: [PATCH 0/3] arm64: queued spinlocks and rw-locks pan xinhui
2017-05-03 18:59 ` pan xinhui
2017-05-04 20:28 ` Yury Norov
2017-05-04 20:28 ` Yury Norov
2017-05-05 11:37 ` 答复: " pan xinhui
2017-05-05 11:37 ` pan xinhui
2017-05-05 11:53 ` Peter Zijlstra
2017-05-05 11:53 ` Peter Zijlstra
2017-05-05 11:53 ` Peter Zijlstra
2017-05-05 12:26 ` Will Deacon
2017-05-05 12:26 ` Will Deacon
2017-05-05 15:28 ` Yury Norov
2017-05-05 15:28 ` Yury Norov
2017-05-05 15:32 ` Will Deacon [this message]
2017-05-05 15:32 ` Will Deacon
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=20170505153245.GH14111@arm.com \
--to=will.deacon@arm.com \
--cc=Andrew.Pinski@cavium.com \
--cc=arnd@arndb.de \
--cc=awallis@codeaurora.org \
--cc=catalin.marinas@arm.com \
--cc=jglauber@cavium.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mnipxh@hotmail.com \
--cc=peterz@infradead.org \
--cc=xinhui.pan@linux.vnet.ibm.com \
--cc=ynorov@caviumnetworks.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.