From: Con Kolivas <kernel@kolivas.org>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>,
"Martin J. Bligh" <mbligh@aracnet.com>
Subject: Re: [PATCH] sched: consider migration thread with smp nice
Date: Tue, 28 Jun 2005 10:48:25 +1000 [thread overview]
Message-ID: <200506281048.29674.kernel@kolivas.org> (raw)
In-Reply-To: <42C09D31.5030207@bigpond.net.au>
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
On Tue, 28 Jun 2005 10:43, Peter Williams wrote:
> Con Kolivas wrote:
> > This patch improves throughput with the smp nice balancing code. Many
> > thanks to Martin Bligh for the usage of his regression testing bed to
> > confirm the effectiveness of various patches.
>
> Con,
> This doesn't build on non SMP systems due to the migration_thread field
> only being defined for SMP. Attached is a copy of a slightly modified
> PlugSched version of the patch which I used to fix the problem in
> PlugSched. Even though it's for a different file it should be easy to
> copy over.
Peter
Look at the actual patch I sent out you'll see it moved the ifdefs up to
compensate. I believe your port of my patch doesn't build and I suspect it's
because you missed these ifdef movements ;)
Cheers,
Con
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-28 0:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-26 8:25 [PATCH] sched: consider migration thread with smp nice Con Kolivas
2005-06-28 0:43 ` Peter Williams
2005-06-28 0:48 ` Con Kolivas [this message]
2005-06-28 2:30 ` Peter Williams
-- strict thread matches above, loose matches on Subject: below --
2005-07-01 11:40 2.6.13-rc1-mm1 Andrew Morton
2005-07-02 0:22 ` [PATCH] sched: consider migration thread with smp nice Con Kolivas
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=200506281048.29674.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=mingo@elte.hu \
--cc=pwil3058@bigpond.net.au \
/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