Messages in this thread | | | From | "Luck, Tony" <> | Subject | RE: [RFC PATCH 02/12] mm: introduce mirror_info | Date | Thu, 4 Jun 2015 16:57:07 +0000 |
| |
+#ifdef CONFIG_MEMORY_MIRROR +struct numa_mirror_info { + int node; + unsigned long start; + unsigned long size; +}; + +struct mirror_info { + int count; + struct numa_mirror_info info[MAX_NUMNODES]; +};
Do we really need this? My patch series leaves all the mirrored memory in the memblock allocator tagged with the MEMBLOCK_MIRROR flag. Can't we use that information when freeing the boot memory into the runtime free lists?
If we can't ... then [MAX_NUMNODES] may not be enough. We may have more than one mirrored range on each node. Current h/w allows two ranges per node.
-Tony
| |