Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751717AbbFZSmw (ORCPT ); Fri, 26 Jun 2015 14:42:52 -0400 Received: from mga09.intel.com ([134.134.136.24]:17882 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751969AbbFZSmp convert rfc822-to-8bit (ORCPT ); Fri, 26 Jun 2015 14:42:45 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,686,1427785200"; d="scan'208";a="735405299" From: "Luck, Tony" To: Xishi Qiu , Kamezawa Hiroyuki CC: Andrew Morton , "nao.horiguchi@gmail.com" , Yinghai Lu , "H. Peter Anvin" , Thomas Gleixner , "mingo@elte.hu" , Xiexiuqi , Hanjun Guo , Linux MM , LKML Subject: RE: [RFC PATCH 10/12] mm: add the buddy system interface Thread-Topic: [RFC PATCH 10/12] mm: add the buddy system interface Thread-Index: AQHQnscWKDg7SoiYFUq3OAjydtKYB52kPxgAgAAwCYCAAR1/gIAYAlaAgADtZ4CAAB5wgIAActqAgAAif4CAABAFMA== Date: Fri, 26 Jun 2015 18:42:41 +0000 Message-ID: <3908561D78D1C84285E8C5FCA982C28F32AA065B@ORSMSX114.amr.corp.intel.com> References: <55704A7E.5030507@huawei.com> <55704CC4.8040707@huawei.com> <557691E0.5020203@jp.fujitsu.com> <5576BA2B.6060907@huawei.com> <5577A9A9.7010108@jp.fujitsu.com> <558BCD95.2090201@huawei.com> <558C94BB.1060304@jp.fujitsu.com> <558CAE43.4090702@huawei.com> <558D0E9B.8030405@jp.fujitsu.com> <558D2B8B.1060901@huawei.com> In-Reply-To: <558D2B8B.1060901@huawei.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.139] 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: 947 Lines: 20 > gfpflags_to_migratetype() > if (memory_mirror_enabled()) { /* We want to mirror all unmovable pages */ > if (!(gfp_mask & __GFP_MOVABLE)) > return MIGRATE_MIRROR > } I'm not sure that we can divide memory into just two buckets of "mirrored" and "movable". My expectation is that there will be memory that is neither mirrored, nor movable. We'd allocate that memory to user proceses. Uncorrected errors in that memory would result in the death of the process (except in the case where the page is a clean copy mapped from a disk file ... e.g. .text mapping instructions from an executable). Linux would offline the affected 4K page so as not to hit the problem again. -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/