From: William Lee Irwin III <wli@holomorphy.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] migration thread fix
Date: Thu, 18 Apr 2002 23:56:32 -0700 [thread overview]
Message-ID: <20020419065632.GD21206@holomorphy.com> (raw)
In-Reply-To: <20020419064851.GC21206@holomorphy.com> <Pine.LNX.4.44.0204190646380.4350-100000@elte.hu>
On Thu, 18 Apr 2002, William Lee Irwin III wrote:
>> I've got a few of those around, I'll see if I can reproduce it. How many
>> cpu's did you need to bring it out?
On Fri, Apr 19, 2002 at 06:48:45AM +0200, Ingo Molnar wrote:
> 2 physical - but i'd suggest to test Erich's patch instead. I had
> debugging code in the scheduler which did printks, which slowed down some
> of the operations in question, such as the startup of the idle thread -
> which created weird situations. [which might not occur in normal testing,
> but which are possible nevertheless.]
That's not many. I'll try it on a bigger one, with a few big fat printk's
in idle task startup and see if I can bring it down. It's an interesting
little tidbit of programming.
As I said earlier, Erich's patch already passed my testing. Thanks though.
Cheers,
Bill
prev parent reply other threads:[~2002-04-19 6:57 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
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 [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=20020419065632.GD21206@holomorphy.com \
--to=wli@holomorphy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox