From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Heiko.Carstens@de.ibm.com
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox), linux-kernel@vger.kernel.org
Subject: Re: CPU attachent and detachment in a running Linux system
Date: Tue, 12 Dec 2000 12:32:12 +0000 (GMT) [thread overview]
Message-ID: <E145obO-000186-00@the-village.bc.nu> (raw)
In-Reply-To: <C12569B3.0024DA06.00@d12mta01.de.ibm.com> from "Heiko.Carstens@de.ibm.com" at Dec 12, 2000 07:42:29 AM
> thanks for your input but I think it won't work this way because the value
> of smp_num_cpus needs to be increased by one right before a new cpu gets
> started. Then one can imagine the following situation at one of the cpus
> that needs to be captured:
This is fine providing the code is aware of the potential race. You capture
all the CPUs up the count by one, set the new cpu going and wait for it
to jump to being captured (even though not by an interrupt) ?
> I still wonder what you and other people think about the idea of an
> interface where the parts of the kernel with per-cpu dependencies should
> register two functions...
The other approach would be too make sure the per CPU structures allocated
which consume little memory have space already for the extra processors - eg
with the arrays of pointers etc
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-12 13:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-12 6:42 Heiko.Carstens
2000-12-12 12:32 ` Alan Cox [this message]
2000-12-15 22:31 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2000-12-21 13:16 Heiko.Carstens
2000-12-18 8:00 Heiko.Carstens
2000-12-18 19:34 ` ferret
2000-12-21 3:21 ` Anton Blanchard
2000-12-11 18:48 Per Jessen
2000-12-11 14:03 Heiko.Carstens
2000-12-11 18:11 ` Matthew D. Pitts
2000-12-11 20:37 ` J . A . Magallon
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=E145obO-000186-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Heiko.Carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®