Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754292AbbFDQ5O (ORCPT ); Thu, 4 Jun 2015 12:57:14 -0400 Received: from mga02.intel.com ([134.134.136.20]:10000 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754270AbbFDQ5J convert rfc822-to-8bit (ORCPT ); Thu, 4 Jun 2015 12:57:09 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,553,1427785200"; d="scan'208";a="705401458" From: "Luck, Tony" To: Xishi Qiu , Andrew Morton , "nao.horiguchi@gmail.com" , Yinghai Lu , "H. Peter Anvin" , Thomas Gleixner , "mingo@elte.hu" , Xiexiuqi , Hanjun Guo CC: Linux MM , LKML Subject: RE: [RFC PATCH 02/12] mm: introduce mirror_info Thread-Topic: [RFC PATCH 02/12] mm: introduce mirror_info Thread-Index: AQHQnsZAivZEKWfWVk2Qj/VDrpAxRZ2cjy7Q Date: Thu, 4 Jun 2015 16:57:07 +0000 Message-ID: <3908561D78D1C84285E8C5FCA982C28F32A8D57F@ORSMSX114.amr.corp.intel.com> References: <55704A7E.5030507@huawei.com> <55704B55.1020403@huawei.com> In-Reply-To: <55704B55.1020403@huawei.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.138] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 834 Lines: 27 +#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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/