All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: nathanl@austin.ibm.com
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org,
	rusty@rustcorp.com.au, Ingo Molnar <mingo@elte.hu>
Subject: Re: [patch 2/2] cpu hotplug notifier for updating sched domains
Date: Wed, 08 Sep 2004 10:44:08 +1000	[thread overview]
Message-ID: <413E55D8.8030608@cyberone.com.au> (raw)
In-Reply-To: <200409071849.i87Inw3f143238@austin.ibm.com>



nathanl@austin.ibm.com wrote:

>Register a cpu hotplug notifier which reinitializes the scheduler
>domains hierarchy.  The notifier temporarily attaches all running cpus
>to a "dummy" domain (like we currently do during boot) to avoid
>balancing.  It then calls arch_init_sched_domains which rebuilds the
>"real" domains and reattaches the cpus to them.
>
>Also change __init attributes to __devinit where necessary.
>
>Signed-off-by: Nathan Lynch <nathanl@austin.ibm.com>
>

Thanks Nathan, this looks great.

I think the next step is to now make the setup code only use cpu_online_map
and get rid of everywhere I had been doing cpus_and(tmp, ..., 
cpu_online_map).
This may also make your patch 1/2 unnecessary? What do you think?

Nick


  reply	other threads:[~2004-09-08  0:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-07 18:50 [patch 2/2] cpu hotplug notifier for updating sched domains nathanl
2004-09-08  0:44 ` Nick Piggin [this message]
2004-09-08  2:05   ` Nathan Lynch
2004-09-08  2:19     ` Nick Piggin
2004-09-08  2:55       ` Nathan Lynch
2004-09-09 10:18       ` Rusty Russell
2004-09-09 10:31         ` Nick Piggin

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=413E55D8.8030608@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nathanl@austin.ibm.com \
    --cc=rusty@rustcorp.com.au \
    /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.