linux-kernel - Re: 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20060825102348.bb53d307.pj@sgi.com>
Date:	Fri, 25 Aug 2006 10:23:48 -0700
From:	Paul Jackson <pj@....com>
To:	Dave Hansen <haveblue@...ibm.com>
Cc:	kamezawa.hiroyu@...fujitsu.com, linux-kernel@...r.kernel.org,
	anton@...ba.org, simon.derr@...l.net, nathanl@...tin.ibm.com,
	akpm@...l.org, y-goto@...fujitsu.com
Subject: Re: memory hotplug - looking for good place for cpuset hook

Dave wrote:
> Gets it a wee bit farther from memory hotplug anyway. ;)

huh?  Where Kame suggested is just a couple lines of code and one test
below where I suggested.  How is this farther from memory hotplug, as
it still seems to be in one of the main memory hotplug routines -
add_memory()?

And why would I want to place a hook that tracks hotplug added memory
nodes 'farther from memory hotplug'?

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