From: Alex Shi <alex.shi@linaro.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [sched/balance] INFO: possible recursive locking detected
Date: Thu, 13 Mar 2014 15:43:11 +0800 [thread overview]
Message-ID: <5321618F.3090801@linaro.org> (raw)
In-Reply-To: <20140303142526.GA8517@localhost>
On 03/03/2014 10:25 PM, Fengguang Wu wrote:
> Greetings,
>
> I got the below dmesg and the first bad commit is
>
> https://github.com/alexshi/power-scheduling.git single-balance.bak
> commit 2adc591a5cb6768ad11e63be9011906aa171148d
> Author: Alex Shi <alex.shi@linaro.org>
> AuthorDate: Fri Feb 28 15:25:09 2014 +0800
> Commit: Alex Shi <alex.shi@linaro.org>
> CommitDate: Sun Mar 2 09:16:38 2014 +0800
>
> sched/balance: replace new_idle_balance
>
> Curren idle_balance will pull task on half of this group. That is
> not needed in central balance.
Thanks for your testing, Fengguang!
I fixed this issue and updated to the git tree. Is the single-balance
branch still in your performance radar? :)
--
Thanks
Alex
next prev parent reply other threads:[~2014-03-13 7:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 14:25 [sched/balance] INFO: possible recursive locking detected Fengguang Wu
2014-03-07 1:59 ` Alex Shi
2014-03-13 7:43 ` Alex Shi [this message]
2014-03-13 8:53 ` Fengguang Wu
2014-03-13 9:00 ` Alex Shi
2014-03-13 9:06 ` Fengguang Wu
2014-03-14 6:16 ` Fengguang Wu
2014-03-14 6:20 ` [sched] 373e9ec30ad: -11.2% qperf.udp_bw.send_bw.MB_sec Fengguang Wu
2014-03-14 6:26 ` [sched/balance] INFO: possible recursive locking detected Alex Shi
2014-03-14 6:48 ` Fengguang Wu
2014-03-14 7:31 ` Alex Shi
2014-03-14 7:40 ` Fengguang Wu
2014-03-14 8:46 ` Alex Shi
2014-03-14 9:06 ` Fengguang Wu
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=5321618F.3090801@linaro.org \
--to=alex.shi@linaro.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).