mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, anton@samba.org,
	simon.derr@bull.net, nathanl@austin.ibm.com, akpm@osdl.org
Subject: memory hotplug - looking for good place for cpuset hook
Date: Fri, 25 Aug 2006 01:53:59 -0700	[thread overview]
Message-ID: <20060825015359.1c9eab45.pj@sgi.com> (raw)

Dave,

I'm looking for a good place to add yet another cpuset hook, this
one to keep a nodemask in my top (root) cpuset always equal to the
current value of node_online_map.

The motivation for this, if you're interested, comes from the
following threads, which added similar cpuset tracking of the
cpu_online_map:

  cpusets not cpu hotplug aware
  http://lkml.org/lkml/2006/8/21/128

  [PATCH] cpuset: top_cpuset tracks hotplug changes to cpu_online_map
  http://lkml.org/lkml/2006/8/24/107

(I cc'd the victims of these threads here, in case they're interested.)

>From what I see so far, the right place to call my cpuset routine to
update its copy of node_online_map would be right after the call:

	node_set_online(nid);

in the routine mm/memory_hotplug.c:add_memory().

Does that seem like a plausible sounding place to you?

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

             reply	other threads:[~2006-08-25  8:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-25  8:53 Paul Jackson [this message]
2006-08-25  9:47 ` KAMEZAWA Hiroyuki
2006-08-25 14:58   ` Dave Hansen
2006-08-25 17:23     ` Paul Jackson
2006-08-25 16:57   ` Paul Jackson
2006-08-25 17:57     ` KAMEZAWA Hiroyuki
2006-08-25 19:01       ` Paul Jackson

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=20060825015359.1c9eab45.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathanl@austin.ibm.com \
    --cc=simon.derr@bull.net \
    /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®