On 6/26/2013 11:37 PM, Yinghai Lu wrote: > On Tue, Jun 25, 2013 at 11:58 AM, Mike Travis <travis@xxxxxxx> wrote: >> experimenting as soon as I can. Our 32TB system is being >> brought back to 16TB (we found a number of problems as we >> get closer and closer to the 64TB limit), but that's still >> a significant size. > > Hi, Mike, > > Can you post e820 memory map on system that have 32TiB or more? > > Is there one range size more than 16TiB? like [16TiB, 32TiB)... > > Thanks > > Yinghai > Here is (was) the 32T system with 2048 cores with HT disabled: BIOS-e820: 0000000000000000 - 000000000007f000 (usable) BIOS-e820: 000000000007f000 - 0000000000080000 (reserved) BIOS-e820: 0000000000080000 - 00000000000a0000 (usable) BIOS-e820: 0000000000100000 - 000000007ad54000 (usable) BIOS-e820: 000000007ad54000 - 000000007ad55000 (reserved) BIOS-e820: 000000007ad55000 - 000000007ad68000 (usable) BIOS-e820: 000000007ad68000 - 000000007afa8000 (reserved) BIOS-e820: 000000007afa8000 - 000000007bcb7000 (usable) BIOS-e820: 000000007bcb7000 - 000000007bdb7000 (reserved) BIOS-e820: 000000007bdb7000 - 000000007beb7000 (unusable) BIOS-e820: 000000007beb7000 - 000000007bfb7000 (reserved) BIOS-e820: 000000007bfb7000 - 000000007d1b7000 (ACPI NVS) BIOS-e820: 000000007d1b7000 - 000000007e000000 (ACPI data) BIOS-e820: 000000007e000000 - 000000007e318000 (usable) BIOS-e820: 000000007e318000 - 000000007ef49000 (ACPI data) BIOS-e820: 000000007ef49000 - 000000007f000000 (usable) BIOS-e820: 0000000100000000 - 0000001e00000000 (usable) BIOS-e820: 0000002000000000 - 0000003dff000000 (usable) BIOS-e820: 0000004000000000 - 0000005dff000000 (usable) BIOS-e820: 0000006000000000 - 0000007dff000000 (usable) .... BIOS-e820: 00000e0000000000 - 00000e1dff000000 (usable) BIOS-e820: 00000e2000000000 - 00000e3dff000000 (usable) BIOS-e820: 00000e4000000000 - 00000e5dff000000 (usable) BIOS-e820: 00000e6000000000 - 00000e7dff000000 (usable) Note that on UV, there is some memory reserved at the end of each node that is used for the directory RAM by the UV HUB. That is why the ranges are not contiguous. I'd have to double check with the BIOS guys, but I don't believe they would have collapsed ranges across nodes even if the directory RAM did not exist. -Mike -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
