From: "chengjian (D)" <cj.chengjian@huawei.com>
To: Will Deacon <will.deacon@arm.com>, <linux-kernel@vger.kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>, <Jeremy.Linton@arm.com>,
<peterz@infradead.org>, <mingo@redhat.com>, <longman@redhat.com>,
<boqun.feng@gmail.com>, <paulmck@linux.vnet.ibm.com>,
"chengjian (D)" <cj.chengjian@huawei.com>,
"Xiexiuqi (Xie XiuQi)" <xiexiuqi@huawei.com>,
"Li Bin" <huawei.libin@huawei.com>, <Waiman.Long@hp.com>
Subject: Re: [PATCH v3 0/5] Switch arm64 over to qrwlock
Date: Sat, 28 Oct 2017 14:10:02 +0800 [thread overview]
Message-ID: <1745f003-ea97-bdce-06fd-a5b80e63979f@huawei.com> (raw)
In-Reply-To: <20171019165332.GD30652@arm.com>
Hi, all.
On 2017/10/20 0:53, Will Deacon wrote:
> I've not had any more feedback on this and the testing results are very
> encouraging so I'd like to merge it for 4.15. However, it might make more
> sense for the whole thing to go via -tip instead.
>
> Ingo, Peter: what do you prefer?
>
> Will
>
>> Will Deacon (5):
>> kernel/locking: Use struct qrwlock instead of struct __qrwlock
>> locking/atomic: Add atomic_cond_read_acquire
>> kernel/locking: Use atomic_cond_read_acquire when spinning in qrwlock
>> arm64: locking: Move rwlock implementation over to qrwlocks
>> kernel/locking: Prevent slowpath writers getting held up by fastpath
>>
>> arch/arm64/Kconfig | 17 ++++
>> arch/arm64/include/asm/Kbuild | 1 +
>> arch/arm64/include/asm/spinlock.h | 164 +-------------------------------
>> arch/arm64/include/asm/spinlock_types.h | 6 +-
>> include/asm-generic/atomic-long.h | 3 +
>> include/asm-generic/qrwlock.h | 37 ++-----
>> include/asm-generic/qrwlock_types.h | 15 ++-
>> include/linux/atomic.h | 4 +
>> kernel/locking/qrwlock.c | 86 +++--------------
>> 9 files changed, 61 insertions(+), 272 deletions(-)
>>
>> --
>> 2.1.4
I am very interested in this change.
Can you share the testing result for me?
Or Test methods, especially test suite and so on.
I would like to further test the performance.
Thanks.
Cheng Jian
prev parent reply other threads:[~2017-10-28 6:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 12:20 Will Deacon
2017-10-12 12:20 ` [PATCH v3 1/5] kernel/locking: Use struct qrwlock instead of struct __qrwlock Will Deacon
2017-10-25 10:13 ` [tip:locking/core] locking/qrwlock: Use 'struct qrwlock' instead of 'struct __qrwlock' tip-bot for Will Deacon
2017-10-12 12:20 ` [PATCH v3 2/5] locking/atomic: Add atomic_cond_read_acquire Will Deacon
2017-10-25 10:14 ` [tip:locking/core] locking/atomic: Add atomic_cond_read_acquire() tip-bot for Will Deacon
2017-10-12 12:20 ` [PATCH v3 3/5] kernel/locking: Use atomic_cond_read_acquire when spinning in qrwlock Will Deacon
2017-10-25 10:14 ` [tip:locking/core] locking/qrwlock: Use atomic_cond_read_acquire() " tip-bot for Will Deacon
2017-10-12 12:20 ` [PATCH v3 4/5] arm64: locking: Move rwlock implementation over to qrwlocks Will Deacon
2017-10-25 10:14 ` [tip:locking/core] locking/qrwlock, arm64: " tip-bot for Will Deacon
2017-10-12 12:20 ` [PATCH v3 5/5] kernel/locking: Prevent slowpath writers getting held up by fastpath Will Deacon
2017-10-25 10:15 ` [tip:locking/core] locking/qrwlock: " tip-bot for Will Deacon
2017-10-12 13:16 ` [PATCH v3 0/5] Switch arm64 over to qrwlock Adam Wallis
2017-10-19 16:53 ` Will Deacon
2017-10-24 14:48 ` Will Deacon
2017-10-24 15:40 ` Ingo Molnar
2017-10-25 8:36 ` Peter Zijlstra
2017-10-28 6:10 ` chengjian (D) [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=1745f003-ea97-bdce-06fd-a5b80e63979f@huawei.com \
--to=cj.chengjian@huawei.com \
--cc=Jeremy.Linton@arm.com \
--cc=Waiman.Long@hp.com \
--cc=boqun.feng@gmail.com \
--cc=huawei.libin@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=will.deacon@arm.com \
--cc=xiexiuqi@huawei.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
all inboxes | Powered by JetHome®