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: <Pine.LNX.4.64.0611151432050.23201@schroedinger.engr.sgi.com>
Date:	Wed, 15 Nov 2006 14:40:36 -0800 (PST)
From:	Christoph Lameter <clameter@....com>
To:	Jack Steiner <steiner@....com>
cc:	Christian Krafft <krafft@...ibm.com>, linux-mm@...ck.org,
	Martin Bligh <mbligh@...igh.org>, linux-kernel@...r.kernel.org
Subject: Re: [patch 2/2] enables booting a NUMA system where some nodes have
 no memory

On Wed, 15 Nov 2006, Jack Steiner wrote:

> A lot of the core infrastructure is currently missing that is required
> to describe IO nodes as regular nodes, but in principle, I don't
> see anything wrong with nodes w/o memory.

Every processor has a local node on which it runs. The kernel places 
memory used by the processor on the local node. Even if we allow
nodes without memory: We still need to associate a "local" node to the 
processor. If that is across some NUMA interlink then it is going to be 
slower but it will work.

AFAIK It seems to be better to explicitly associate a memory node with a 
processor during bootup in arch code. 

Various kernel optimizations rely on local memory. Would we create 
a  special case here of a pglist_data structure without a zones structure? 

It seems that the contents of pglist_data are targeted to a memory node. 
If we do not have a pglist_data structure then the node would not exist 
for the kernel.

What would the benefit or difference be of having nodes without memory?
-
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