| 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
| ||
|
Message-ID: <8922EB9A36049040806AD0C06C26CAAF45120C7A@fmsmsx117.amr.corp.intel.com> Date: Tue, 31 Mar 2015 17:16:53 +0000 From: "Brooks, Adam J" <adam.j.brooks@...el.com> To: Boaz Harrosh <boaz@...xistor.com>, Christoph Hellwig <hch@....de> CC: "axboe@...nel.dk" <axboe@...nel.dk>, "linux-nvdimm@...1.01.org" <linux-nvdimm@...1.01.org>, "x86@...nel.org" <x86@...nel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org> Subject: RE: [Linux-nvdimm] [PATCH 1/6] SQUASHME: Don't let e820_PMEM sections >If we need a NUMA crossing a mids a contiguous memory range >we split the range at NUMA boundary so to produce two pmemX >devices. We do not like 2 NUMA IDs at the same device. > >TODO: What happens with real type-12 NvDIMM the BIOS splits >these ranges? The physical memory map for an Intel based dual socket system supporting NVDIMMS will be: Socket 0 Normal Memory Socket 0 NVDIMMs Socket 1 Normal Memory Socket 1 NVDIMMs If you have both NVDIMMs and normal DIMMs on both sockets you will see two separate ranges. If there are NVDIMMs on both sockets, but no normal memory on socket 1, then you will end up with a single range covering the NVDIMMs on both sockets. -- 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