From: William Lee Irwin III <wli@holomorphy.com>
To: Erich Focht <efocht@ess.nec.de>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
torvalds@transmeta.com
Subject: Re: [PATCH] migration thread fix
Date: Thu, 18 Apr 2002 14:28:51 -0700 [thread overview]
Message-ID: <20020418212851.GW21206@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0204182043110.2453-100000@beast.local>
On Thu, Apr 18, 2002 at 10:08:55PM +0200, Erich Focht wrote:
> The patch below applies to the 2.5.8 kernel. It does two things:
> 1: Fixes a BUG in the migration threads: the interrupts MUST be disabled
> before the double runqueue lock is aquired, otherwise this thing will
> deadlock sometimes.
> 2: Streamlines the initialization of migration threads. Instead of
> fiddling around with cache_deccay_ticks, waiting for migration_mask bits
> and relying on the scheduler to distribute the tasks uniformly among
> processors, it starts the migration thread on the boot cpu and uses it to
> reliably distribute the other threads to their target cpus.
> Please consider applying it!
I have a patch to fix #2 as well. Did you see it? Did you try it?
Cheers,
Bill
next prev parent reply other threads:[~2002-04-18 21:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 20:08 [PATCH] migration thread fix Erich Focht
2002-04-18 21:28 ` William Lee Irwin III [this message]
2002-04-18 21:41 ` Robert Love
2002-04-18 22:07 ` Anton Blanchard
2002-04-18 22:27 ` Robert Love
2002-04-18 22:24 ` Erich Focht
2002-04-18 22:38 ` Robert Love
2002-04-18 23:27 ` William Lee Irwin III
2002-04-19 1:51 ` Erich Focht
2002-04-19 2:30 ` William Lee Irwin III
2002-04-19 8:09 ` Erich Focht
2002-04-19 4:31 ` Ingo Molnar
2002-04-19 6:40 ` William Lee Irwin III
2002-04-19 4:41 ` Ingo Molnar
2002-04-19 6:48 ` William Lee Irwin III
2002-04-19 4:48 ` Ingo Molnar
2002-04-19 6:56 ` William Lee Irwin III
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=20020418212851.GW21206@holomorphy.com \
--to=wli@holomorphy.com \
--cc=efocht@ess.nec.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox