Re: [Bug fix PATCH 1/2] acpi, movablemem_map: Exclude memblock.reserved ranges when parsing SRAT.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Tony,

On 02/21/2013 06:41 AM, Luck, Tony wrote:
What's the relationship between e820 map and SRAT?
The e820 map (or EFI memory map on some recent systems) provides
a list of memory ranges together with usage information (e.g. reserved
for BIOS, or available) and attributes (WB cacheable, uncacheable).

The SRAT table provides topology information for address ranges. It
tells the OS which memory is close to each cpu, and which is more
distant. If there are multiple degrees of "distant" then the SLIT table
provides a matrix of relative latencies between nodes.

Thanks for your clarify. What's the relationship between memory ranges and address ranges here?
What's the relationship between memory/address ranges and /proc/iomem?


-Tony

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]