All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: unpredictability in scheduler test results -- still present
Date: Mon, 29 Sep 2008 09:43:53 -0600	[thread overview]
Message-ID: <48E0F7B9.3040301@nortel.com> (raw)
In-Reply-To: <20080927200433.GC28937@elte.hu>

Ingo Molnar wrote:
> * Chris Friesen <cfriesen@nortel.com> wrote:

>> It turns out that disabling CONFIG_DYNAMIC_FTRACE makes the load 
>> balancing problem go away and causes all cpus to be used.
>>
>> With this option enabled, the problem seems to be present as far back 
>> as 2.6.27-rc2.  (2.6.27-rc1 doesn't compile on my machine, and 2.6.26 
>> doesn't have ftrace).
>>
>> I have no idea why turning on dynamic ftrace would affect load 
>> balancing behaviour, but it's very repeatable.  The very first test 
>> run after booting works fine, and all successive runs fail to balance 
>> properly.

> OTOH, what does 'truning on dftrace' exactly mean? Just enabling it in 
> the .config, or also activating it via /debug/tracing/current_tracer?

Just enabling it in the .config is enough to trigger the behaviour 
change.  I'm not explicitly activating any traces.

Chris

  reply	other threads:[~2008-09-29 15:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-18 22:45 unpredictability in scheduler test results Chris Friesen
2008-09-24 15:19 ` unpredictability in scheduler test results -- still present Chris Friesen
2008-09-24 23:37   ` Chris Friesen
2008-09-27 20:04     ` Ingo Molnar
2008-09-29 15:43       ` Chris Friesen [this message]
2008-09-30 11:12         ` Ingo Molnar
2008-09-30 21:14           ` Chris Friesen

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=48E0F7B9.3040301@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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.