From: John Stultz <johnstul@us.ibm.com>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: rcu stalls seen with numasched_v2 patches applied.
Date: Tue, 07 Aug 2012 10:08:51 -0700 [thread overview]
Message-ID: <50214BA3.8030909@us.ibm.com> (raw)
In-Reply-To: <20120807123305.GA7137@linux.vnet.ibm.com>
On 08/07/2012 05:33 AM, Srikar Dronamraju wrote:
> Hi,
>
> I saw this while I was running the 2nd August -tip kernel + Peter's
> numasched patches.
>
> Top showed load average to be 240, there was one cpu (cpu 7) which
> showed 100% while all other cpus were idle. The system showed some
> sluggishness. Before I saw this I ran Andrea's autonuma benchmark couple
> of times.
>
> I am not sure if this is an already reported issue/known issue.
So Ingo pushed a fix the other day that might address this:
http://git.linaro.org/gitweb?p=people/jstultz/linux.git;a=commitdiff_plain;h=1d17d17484d40f2d5b35c79518597a2b25296996
But do let me know any reproduction details if you can trigger this
again. If you do trigger it again without that patch, watch to see if
the time value from date is running much faster then it should.
thanks
-john
next prev parent reply other threads:[~2012-08-07 17:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 12:33 rcu stalls seen with numasched_v2 patches applied Srikar Dronamraju
2012-08-07 13:52 ` Peter Zijlstra
2012-08-07 17:19 ` Srikar Dronamraju
2012-08-08 19:58 ` Peter Zijlstra
2012-08-10 16:24 ` Srikar Dronamraju
2012-08-13 7:51 ` Peter Zijlstra
2012-08-13 8:11 ` Peter Zijlstra
2012-08-16 17:16 ` Srikar Dronamraju
2012-08-17 5:23 ` Srikar Dronamraju
2012-08-07 17:08 ` John Stultz [this message]
2012-08-07 16:59 ` Srikar Dronamraju
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=50214BA3.8030909@us.ibm.com \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=srikar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox