From: Nick Piggin <piggin@cyberone.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org, dipankar@in.ibm.com,
vatsa@in.ibm.com, mingo@redhat.com
Subject: Re: [PATCH 3/4] 2.6.2-rc2-mm2 CPU Hotplug: The Core
Date: Sun, 01 Feb 2004 21:19:34 +1100 [thread overview]
Message-ID: <401CD2B6.3040803@cyberone.com.au> (raw)
In-Reply-To: <20040201000314.233e05a7.akpm@osdl.org>
Andrew Morton wrote:
>Rusty Russell <rusty@rustcorp.com.au> wrote:
>
>> The actual CPU patch. It's big, but almost all under
>> CONFIG_HOTPLUG_CPU, or macros which have same effect.
>>
>
>Needs a fixup.
>
>
>
>CPU_MASK_ALL and CPU_MASK_NONE may only be used for initialisers. It
>doesn't compile if NR_CPUS>4*BITS_PER_LONG. Fixes to the cpumask
>infrastructure for this remain welcome.
>
>
The kernel/sched.c stuff otherwise looks pretty straightforward
at a quick glance. I can't see any fundamental problem with it.
next prev parent reply other threads:[~2004-02-01 10:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-31 14:16 [PATCH 3/4] 2.6.2-rc2-mm2 CPU Hotplug: The Core Rusty Russell
2004-02-01 8:03 ` Andrew Morton
2004-02-01 10:19 ` Nick Piggin [this message]
2004-02-01 12:07 ` Rusty Russell
2004-02-02 9:12 ` Ingo Molnar
2004-02-02 10:55 ` Rusty Russell
2004-02-02 12:45 ` Ingo Molnar
2004-02-02 13:22 ` Srivatsa Vaddagiri
2004-02-02 15:40 ` Ingo Molnar
2004-02-03 0:45 ` Rusty Russell
2004-02-03 8:04 ` Ingo Molnar
2004-02-03 8:16 ` Rusty Russell
2004-02-03 8:31 ` Ingo Molnar
2004-02-03 7:39 ` New v. v. experimental HOTPLUG CPU megapatch Rusty Russell
2004-02-03 9:35 ` Ingo Molnar
2004-02-05 18:12 ` Pavel Machek
2004-02-03 0:34 ` [PATCH 3/4] 2.6.2-rc2-mm2 CPU Hotplug: The Core Rusty Russell
2004-02-03 9:26 ` Ingo Molnar
2004-02-04 0:19 ` Rusty Russell
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=401CD2B6.3040803@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=vatsa@in.ibm.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.