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: <1156517885.12011.170.camel@localhost.localdomain>
Date:	Fri, 25 Aug 2006 07:58:05 -0700
From:	Dave Hansen <haveblue@...ibm.com>
To:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc:	Paul Jackson <pj@....com>, linux-kernel@...r.kernel.org,
	anton@...ba.org, simon.derr@...l.net, nathanl@...tin.ibm.com,
	akpm@...l.org, GOTO <y-goto@...fujitsu.com>
Subject: Re: memory hotplug - looking for good place for cpuset hook

On Fri, 2006-08-25 at 18:47 +0900, KAMEZAWA Hiroyuki wrote:
> 
> if (new_pgdat) {
>         register_one_node(nid); <-- add sysfs entry of node
>         <here>
> }
> 
> is good.
> 
> (When I implements node-hotplug invoked by cpu-hotplug, I'll care
> cpuset.) 

Looks like someone beat me to the punch.  Putting it in there would be
fine with me.  Gets it a wee bit farther from memory hotplug anyway. ;)

-- Dave

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ