linux-kernel - memory hotplug - looking for good place for cpuset hook

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20060825015359.1c9eab45.pj@sgi.com>
Date:	Fri, 25 Aug 2006 01:53:59 -0700
From:	Paul Jackson <pj@....com>
To:	Dave Hansen <haveblue@...ibm.com>
Cc:	linux-kernel@...r.kernel.org, anton@...ba.org, simon.derr@...l.net,
	nathanl@...tin.ibm.com, akpm@...l.org
Subject: memory hotplug - looking for good place for cpuset hook

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@....com> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/