From: Andi Kleen <ak@suse.de>
To: yhlu <yhlu.kernel@gmail.com>
Cc: Andi Kleen <ak@suse.de>, Mike Waychison <mikew@google.com>,
YhLu <YhLu@tyan.com>, Peter Buckingham <peter@pantasys.com>,
linux-kernel@vger.kernel.org,
"discuss@x86-64.org" <discuss@x86-64.org>
Subject: Re: [discuss] Re: 2.6.13-rc2 with dual way dual core ck804 MB
Date: Thu, 11 Aug 2005 02:51:00 +0200 [thread overview]
Message-ID: <20050811005100.GF8974@wotan.suse.de> (raw)
In-Reply-To: <86802c440508101743783588df@mail.gmail.com>
On Wed, Aug 10, 2005 at 05:43:23PM -0700, yhlu wrote:
> Yes, I mean more aggressive
>
> static void __init smp_init(void)
> {
> unsigned int i;
>
> /* FIXME: This should be done in userspace --RR */
> for_each_present_cpu(i) {
> if (num_online_cpus() >= max_cpus)
> break;
> if (!cpu_online(i))
> cpu_up(i);
> }
>
>
> let cpu_up take one array instead of one int.
It can be done already by just not starting the CPUs and
then do it multithreaded from user space using sysfs with
the CPU hotplug infrastructure. Unfortunately cpu_up
right now has a global semaphore, so it won't save you any
time. However it could be done in parallel with other
startup jobs.
-Andi
next prev parent reply other threads:[~2005-08-11 0:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 0:56 2.6.13-rc2 with dual way dual core ck804 MB YhLu
2005-08-10 23:14 ` Mike Waychison
2005-08-10 23:26 ` [discuss] " Andi Kleen
2005-08-10 23:42 ` yhlu
2005-08-11 0:04 ` Andi Kleen
2005-08-11 0:17 ` yhlu
2005-08-11 0:23 ` yhlu
2005-08-11 0:28 ` Andi Kleen
2005-08-11 0:43 ` yhlu
2005-08-11 0:51 ` Andi Kleen [this message]
2005-08-12 6:59 ` yhlu
2005-08-12 7:04 ` yhlu
2005-08-12 13:07 ` Andi Kleen
2005-08-12 16:18 ` yhlu
2005-08-12 16:41 ` Andi Kleen
2005-08-12 17:36 ` yhlu
2005-08-10 23:49 ` Mike Waychison
2005-08-10 23:31 ` Peter Buckingham
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=20050811005100.GF8974@wotan.suse.de \
--to=ak@suse.de \
--cc=YhLu@tyan.com \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikew@google.com \
--cc=peter@pantasys.com \
--cc=yhlu.kernel@gmail.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