linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@linuxcare.com.au>
To: Heiko.Carstens@de.ibm.com
Cc: Pavel Machek <pavel@suse.cz>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: CPU attachent and detachment in a running Linux system
Date: Thu, 21 Dec 2000 14:21:35 +1100	[thread overview]
Message-ID: <20001221142135.G6183@linuxcare.com> (raw)
In-Reply-To: <C12569B9.002C03CF.00@d12mta01.de.ibm.com>
In-Reply-To: <C12569B9.002C03CF.00@d12mta01.de.ibm.com>; from Heiko.Carstens@de.ibm.com on Mon, Dec 18, 2000 at 09:00:43AM +0100

 
> 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.

I remember someone from SGI had a patch to merge all the per cpu structures
together which would make this easier. It would also save bytes especially
on machines like the e10k where we must have NR_CPUS = 64.

Anton
-
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/

  parent reply	other threads:[~2000-12-21  3:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-18  8:00 CPU attachent and detachment in a running Linux system Heiko.Carstens
2000-12-18 19:34 ` ferret
2000-12-21  3:21 ` Anton Blanchard [this message]
  -- 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=20001221142135.G6183@linuxcare.com \
    --to=anton@linuxcare.com.au \
    --cc=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;
as well as URLs for NNTP newsgroup(s).