From: Yuyang Du <yuyang.du@intel.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>,
Andrey Ryabinin <a.ryabinin@samsung.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: sched: odd values for effective load calculations
Date: Tue, 16 Dec 2014 10:09:48 +0800 [thread overview]
Message-ID: <20141216020948.GA6399@intel.com> (raw)
In-Reply-To: <548FBA62.5090603@oracle.com>
On Mon, Dec 15, 2014 at 11:51:46PM -0500, Sasha Levin wrote:
> On 12/15/2014 07:12 AM, Peter Zijlstra wrote:
> >
> > Sorry for the long delay, I was out for a few weeks due to having become
> > a dad for the second time.
>
> Congrats! May you be able to sleep at night sooner rather than later.
Congrats +1.
>
> It's fairy reproducible, I've seen it happen quite a few times. What other
> information might be useful?
>
Sasha, it might be helpful to see this_load is from:
this_load1: this_load = target_load(this_cpu, idx);
or
this_load2: this_load += effective_load(tg, this_cpu, -weight, -weight);
It really does not seem to be this_load1, while the calc of effective_load is a bit
complicated to see what the problem is.
next prev parent reply other threads:[~2014-12-16 10:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 22:53 sched: odd values for effective load calculations Sasha Levin
2014-12-13 8:30 ` Ingo Molnar
2014-12-15 12:12 ` Peter Zijlstra
2014-12-15 13:14 ` Peter Zijlstra
2014-12-16 5:29 ` Sasha Levin
2014-12-16 15:37 ` Peter Zijlstra
2014-12-18 2:10 ` Yuyang Du
2014-12-16 4:51 ` Sasha Levin
2014-12-16 2:09 ` Yuyang Du [this message]
2014-12-19 0:29 ` Yuyang Du
2014-12-19 11:20 ` Peter Zijlstra
2015-01-09 12:33 ` [tip:sched/urgent] sched: Fix odd values in effective_load() calculations tip-bot for Yuyang Du
2014-12-16 15:33 ` sched: odd values for effective load calculations Peter Zijlstra
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=20141216020948.GA6399@intel.com \
--to=yuyang.du@intel.com \
--cc=a.ryabinin@samsung.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=sasha.levin@oracle.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.