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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 28 Oct 2009 02:03:41 -0700 (PDT) From: David Rientjes <rientjes@...gle.com> To: Heiko Carstens <heiko.carstens@...ibm.com> cc: Alex Chiang <achiang@...com>, Andrew Morton <akpm@...ux-foundation.org>, Gary Hade <garyhade@...ibm.com>, linux-kernel@...r.kernel.org, linux-mm@...ck.org, Badari Pulavarty <pbadari@...ibm.com>, Martin Schwidefsky <schwidefsky@...ibm.com>, Ingo Molnar <mingo@...e.hu> Subject: Re: [PATCH v2 1/5] mm: add numa node symlink for memory section in sysfs On Wed, 28 Oct 2009, Heiko Carstens wrote: > The short answer is: s390 doesn't support NUMA, because the hardware doesn't > tell us to which node (book in s390 terms) a memory range belongs to. > > Memory layout for a logical partition is striped: first x mbyte belong to > node 0, next x mbyte belong to node 1, etc... > > Also, since there is always a hypervisor running below Linux I don't think > it would make too much sense if we would know to which node a piece of > memory belongs to: if the hypervisor decides to schedule a virtual cpu of > a logical partition to a different node then what? > Ok, so the patchset is a no-op for s390 since it only utilizes the !CONFIG_NUMA code. Alex, I think the safest thing to do in unregister_mem_sect_under_nodes() is to iterate though the section pfns and remove links to the node_device kobjs for all the distinct pfn_to_nid()'s that it encounters. -- 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