All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	Linux kernel <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [bug report] sched: stop_machine() usage causes load balancer to misbehave
Date: Fri, 03 Oct 2008 23:27:21 -0600	[thread overview]
Message-ID: <48E6FEB9.8070603@nortel.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0810022001250.26504@gandalf.stny.rr.com>

Steven Rostedt wrote:
> On Thu, 2 Oct 2008, Chris Friesen wrote:
> 
> 
>>I mentioned before that ftrace (specifically the ftraced daemon) seems to be
>>interfering with the load balancer.  After some experimenting, it appears that
>>any regular calls to stop_machine() will end up confusing the load balancer.
>>
>>As an experiment, I disabled ftraced (which would normally result in correct
>>load balancing) but added a single kernel thread which simply runs the
>>following loop, where "chrisd2" is a dummy function.
> 
> 
> 
> Chris,
> 
> Thanks for looking into this. I don't have an answer for your question, 
> but I'll work harder to get the MCOUNT_REC working in PPC.
> 
> Does this happen with x86 too?

Unfortunately I don't have an x86 box handy for testing...I could 
probably get some time on a lab machine next week.

Chris

      reply	other threads:[~2008-10-04  5:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02 23:57 [bug report] sched: stop_machine() usage causes load balancer to misbehave Chris Friesen
2008-10-03  0:02 ` Steven Rostedt
2008-10-04  5:27   ` Chris Friesen [this message]

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=48E6FEB9.8070603@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.