All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyrus Massoumi <cyrusm@gmx.net>
To: Micah Dowty <micah@vmware.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: High priority tasks break SMP balancer?
Date: Sat, 10 Nov 2007 00:56:07 +0100	[thread overview]
Message-ID: <4734F397.7080802@gmx.net> (raw)
In-Reply-To: <20071109223417.GB16250@vmware.com>

Hi Micah

> On my machine (2-way Opteron with a vanilla 2.6.23.1 kernel) this test
> program will reliably put the scheduler into a state where one CPU has
> both of the busy-looping processes in its runqueue, and the other CPU
> is usually idle. The usually-idle CPU will have a very high cpu_load,
> as reported by /proc/sched_debug.

I tried your program on my machine (C2D, 2.6.17, O(1) scheduler).

Both CPUs are 100% busy all the time. Each busy-looping thread is 
running on its own CPU. I've been watching top output for 10 minutes, 
the spreading is stable and the threads don't bounce at all.


greetings
Cyrus



  reply	other threads:[~2007-11-09 23:55 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-09 22:34 High priority tasks break SMP balancer? Micah Dowty
2007-11-09 23:56 ` Cyrus Massoumi [this message]
2007-11-10  0:11   ` Micah Dowty
2007-11-14 18:39     ` Micah Dowty
2007-11-15 18:48     ` Kyle Moffett
2007-11-15 19:14       ` Micah Dowty
2007-11-15 20:07         ` Christoph Lameter
2007-11-15 20:24           ` Micah Dowty
2007-11-15 21:28             ` Christoph Lameter
2007-11-15 21:35               ` Micah Dowty
2007-11-16  2:31                 ` Christoph Lameter
2007-11-16  2:44                   ` Micah Dowty
2007-11-16  6:07                     ` Ingo Molnar
2007-11-16  9:19                       ` Micah Dowty
2007-11-16 10:45                         ` Ingo Molnar
2007-11-16 10:48                       ` Micah Dowty
2007-11-16 22:12                         ` Christoph Lameter
2007-11-16 10:48                       ` Dmitry Adamushko
2007-11-16 22:14                         ` Micah Dowty
2007-11-16 23:26                           ` Dmitry Adamushko
2007-11-17  1:03                             ` Micah Dowty
2007-11-17 19:10                               ` Dmitry Adamushko
2007-11-19 18:51                                 ` Micah Dowty
2007-11-19 22:22                                   ` Dmitry Adamushko
2007-11-19 23:05                                     ` Micah Dowty
2007-11-20  5:57                                       ` Ingo Molnar
2007-11-20 18:06                                         ` Micah Dowty
2007-11-20 21:47                                           ` Dmitry Adamushko
2007-11-22  7:46                                             ` Micah Dowty
2007-11-22 12:53                                               ` Dmitry Adamushko
2007-11-26 19:44                                                 ` Micah Dowty
2007-11-27  9:21                                                   ` Dmitry Adamushko
2007-11-27 17:13                                                     ` Micah Dowty
2007-11-16 19:13         ` David Newall
2007-11-16 21:38           ` Micah Dowty

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=4734F397.7080802@gmx.net \
    --to=cyrusm@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=micah@vmware.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 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.