From: Nick Piggin <nickpiggin@yahoo.com.au>
To: John Hawkes <hawkes@sgi.com>
Cc: John Hawkes <hawkes@google.engr.sgi.com>,
John Hawkes <hawkes@oss.sgi.com>, Ingo Molnar <mingo@elte.hu>,
jbarnes@sgi.com, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH, 2.6.9] improved load_balance() tolerance for pinned tasks
Date: Sat, 23 Oct 2004 14:27:15 +1000 [thread overview]
Message-ID: <4179DDA3.1020405@yahoo.com.au> (raw)
In-Reply-To: <00ee01c4b870$030b80f0$6700a8c0@comcast.net>
John Hawkes wrote:
> From: "John Hawkes" <hawkes@google.engr.sgi.com>
>
>>No, your variation doesn't solve the problem. This variation of your
>>patch does, however, solve the problem. The difference is in
>>move_tasks():
>
>
> Actually, there is another related problem that arises in
> active_load_balance() with a runqueue that holds hundreds of pinned processes.
> I'm seeing a migration_thread perpetually consuming 70% of its CPU.
>
That's what I was worried about, but in your most recent
patch you just sent, the all_pinned path should skip over
the active load balance completely... basically it shouldn't
be running at all, and if it is then it is a bug I think?
next prev parent reply other threads:[~2004-10-23 4:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 19:36 [PATCH, 2.6.9] improved load_balance() tolerance for pinned tasks John Hawkes
2004-10-20 19:59 ` Ingo Molnar
2004-10-22 13:08 ` Nick Piggin
2004-10-22 19:38 ` John Hawkes
[not found] ` <00ee01c4b870$030b80f0$6700a8c0@comcast.net>
2004-10-23 4:27 ` Nick Piggin [this message]
2004-10-25 16:02 ` John Hawkes
2004-10-25 23:59 ` Nick Piggin
2004-10-30 0:21 ` Matthew Dobson
-- strict thread matches above, loose matches on Subject: below --
2004-10-22 19:20 John Hawkes
2004-10-23 4:22 ` Nick Piggin
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=4179DDA3.1020405@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=hawkes@google.engr.sgi.com \
--cc=hawkes@oss.sgi.com \
--cc=hawkes@sgi.com \
--cc=jbarnes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.