From: qiaozhou <qiaozhou@asrmicro.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Vikram Mulukutla <markivx@codeaurora.org>,
Thomas Gleixner <tglx@linutronix.de>,
John Stultz <john.stultz@linaro.org>, <sboyd@codeaurora.org>,
LKML <linux-kernel@vger.kernel.org>,
Wang Wilbur <wilburwang@asrmicro.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
<linux-kernel-owner@vger.kernel.org>, <sudeep.holla@arm.com>
Subject: Re: [Question]: try to fix contention between expire_timers and try_to_del_timer_sync
Date: Wed, 11 Oct 2017 16:33:03 +0800 [thread overview]
Message-ID: <bf81be7b-4d6c-acd4-4f80-b8cfbbee625f@asrmicro.com> (raw)
In-Reply-To: <20171002141400.GB12847@arm.com>
Hi Will,
On 2017年10月02日 22:14, Will Deacon wrote:
> Hi Qiao,
>
> On Mon, Sep 25, 2017 at 07:02:03PM +0800, qiaozhou wrote:
>> Will this bodging patch be merged? It can solve the livelock issue on arm64
>> platforms(at least improve a lot).
>
> Whilst it seemed to help in some cases, I'm not keen to merge it until
> we've identified a sensible way to parameterise the threshold and also
> explain why it doens't appear to help at all on some platforms. I guess
> I could respin a version that takes the threshold on the cmdline and
> also checks to see that the event stream is enabled, since that might
> help with further benchmarking.
>
> Would that be useful?
Got it. Please let me know if you want to verify it on my platform. Many
thanks.
Best Regards
Qiao
prev parent reply other threads:[~2017-10-11 8:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3d2459c7-defd-a47e-6cea-007c10cecaac@asrmicro.com>
2017-07-26 14:16 ` Thomas Gleixner
2017-07-27 1:29 ` qiaozhou
2017-07-27 15:14 ` Will Deacon
2017-07-27 15:19 ` Thomas Gleixner
2017-07-28 1:10 ` Vikram Mulukutla
2017-07-28 9:28 ` Peter Zijlstra
2017-07-28 19:11 ` Vikram Mulukutla
2017-07-28 9:28 ` Will Deacon
2017-07-28 19:09 ` Vikram Mulukutla
2017-07-31 11:20 ` qiaozhou
2017-08-01 7:37 ` qiaozhou
2017-08-03 23:32 ` Vikram Mulukutla
2017-08-04 3:15 ` qiaozhou
2017-07-31 13:13 ` Will Deacon
2017-08-03 23:25 ` Vikram Mulukutla
2017-08-15 18:40 ` Will Deacon
2017-08-25 19:48 ` Vikram Mulukutla
2017-08-25 20:25 ` Vikram Mulukutla
2017-08-28 23:12 ` Vikram Mulukutla
2017-09-06 11:19 ` qiaozhou
2017-09-25 11:02 ` qiaozhou
2017-10-02 14:14 ` Will Deacon
2017-10-11 8:33 ` qiaozhou [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=bf81be7b-4d6c-acd4-4f80-b8cfbbee625f@asrmicro.com \
--to=qiaozhou@asrmicro.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel-owner@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=markivx@codeaurora.org \
--cc=peterz@infradead.org \
--cc=sboyd@codeaurora.org \
--cc=sudeep.holla@arm.com \
--cc=tglx@linutronix.de \
--cc=wilburwang@asrmicro.com \
--cc=will.deacon@arm.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
Powered by JetHome