From: Heiko.Carstens@de.ibm.com
To: Pavel Machek <pavel@suse.cz>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: CPU attachent and detachment in a running Linux system
Date: Mon, 18 Dec 2000 09:00:43 +0100 [thread overview]
Message-ID: <C12569B9.002C03CF.00@d12mta01.de.ibm.com> (raw)
Hi,
>> 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...
>Why not compile kernel with structeres big enough for 32 processors,
>and then just add CPUs up to the limit without changing anything?
That's a good point and it would probably work for attachment of cpus, but
it won't work for detachment because there are some data structures that
need to be updated if a cpu gets detached. For example it would be nice
to flush the per-cpu cache of the detached cpu in the slabcache. Then one
has to think of pending tasklets for the detached cpu which should be
moved to another cpu and then there are a lot of per-cpu data structures
in the networking part of the kernel.. most of them seem to be for
statistics only but I think these structures should be updated in any
case.
So at least for detaching it would make sense to register functions which
will be called whenever a cpu gets detached.
Heiko
-
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 reply other threads:[~2000-12-18 8:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-18 8:00 Heiko.Carstens [this message]
2000-12-18 19:34 ` CPU attachent and detachment in a running Linux system ferret
2000-12-21 3:21 ` Anton Blanchard
-- strict thread matches above, loose matches on Subject: below --
2000-12-21 13:16 Heiko.Carstens
2000-12-12 6:42 Heiko.Carstens
2000-12-12 12:32 ` Alan Cox
2000-12-15 22:31 ` Pavel Machek
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=C12569B9.002C03CF.00@d12mta01.de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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