From: Mike Galbraith <efault@gmx.de>
To: Lin Ming <ming.m.lin@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
"Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: netperf ~50% regression with 2.6.33-rc1, bisect to 1b9508f
Date: Mon, 25 Jan 2010 12:45:13 +0100 [thread overview]
Message-ID: <1264419913.5888.49.camel@marge.simson.net> (raw)
In-Reply-To: <1264419342.5888.42.camel@marge.simson.net>
On Mon, 2010-01-25 at 12:35 +0100, Mike Galbraith wrote:
> So. Rummaging around doing absolutely _nothing_ useful, there being
> zero movable tasks in this load, prevents us switching to the idle
> thread before the scheduling task is requeued. Oh joy.
Wait a minute. The only way that can work is if we hit contended lock,
and drop our rq lock (and where would busiest->nr_running > 1 come from
with a 2 task load?)
Puzzled.
-Mike
next prev parent reply other threads:[~2010-01-25 11:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 10:03 netperf ~50% regression with 2.6.33-rc1, bisect to 1b9508f Lin Ming
2010-01-25 11:35 ` Mike Galbraith
2010-01-25 11:45 ` Mike Galbraith [this message]
2010-01-26 9:03 ` Lin Ming
2010-01-25 14:03 ` Peter Zijlstra
2010-01-25 14:19 ` Mike Galbraith
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=1264419913.5888.49.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=yanmin_zhang@linux.intel.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