From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io0-f171.google.com (mail-io0-f171.google.com [209.85.223.171]) by kanga.kvack.org (Postfix) with ESMTP id F17EB6B0005 for ; Sun, 28 Feb 2016 21:12:56 -0500 (EST) Received: by mail-io0-f171.google.com with SMTP id g203so172719460iof.2 for ; Sun, 28 Feb 2016 18:12:56 -0800 (PST) Received: from mgwkm03.jp.fujitsu.com (mgwkm03.jp.fujitsu.com. [202.219.69.170]) by mx.google.com with ESMTPS id vv11si15316484igb.55.2016.02.28.18.12.55 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 28 Feb 2016 18:12:56 -0800 (PST) Received: from g01jpfmpwyt03.exch.g01.fujitsu.local (g01jpfmpwyt03.exch.g01.fujitsu.local [10.128.193.57]) by kw-mxoi2.gw.nic.fujitsu.com (Postfix) with ESMTP id 2AA78AC00E4 for ; Mon, 29 Feb 2016 11:12:51 +0900 (JST) From: "Izumi, Taku" Subject: [LSF/MM ATTEND][LSF/MM TOPIC] Address range mirroring enhancement Date: Mon, 29 Feb 2016 02:12:49 +0000 Message-ID: Content-Language: ja-JP Content-Type: text/plain; charset="iso-2022-jp" MIME-Version: 1.0 Sender: owner-linux-mm@kvack.org List-ID: To: "lsf-pc@lists.linux-foundation.org" , "linux-mm@kvack.org" Cc: Tony Luck , Xishi Qiu Hi, I'd like to atten LSF/MM 2016 and I'd like to discuss "Address range mirroring" topic. The current status of Address range mirroring in Linux is: - bootmem will be allocated from mirroring range - kernel memorry will be allocated from mirroring range by specifying kernelcore=mirror I think we can enhance Adderss range mirroring more. For excample, - The handling of mirrored memory exhaustion case - The option any user memory can be allocated from mirrored memory and so on. I'd like to discuss this topic. Sincerely, Taku Izumi -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f173.google.com (mail-pf0-f173.google.com [209.85.192.173]) by kanga.kvack.org (Postfix) with ESMTP id B594F6B0005 for ; Mon, 29 Feb 2016 00:01:52 -0500 (EST) Received: by mail-pf0-f173.google.com with SMTP id 124so23880169pfg.0 for ; Sun, 28 Feb 2016 21:01:52 -0800 (PST) Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com. [2607:f8b0:400e:c03::22c]) by mx.google.com with ESMTPS id z7si3996431par.63.2016.02.28.21.01.51 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 28 Feb 2016 21:01:51 -0800 (PST) Received: by mail-pa0-x22c.google.com with SMTP id fl4so85354887pad.0 for ; Sun, 28 Feb 2016 21:01:51 -0800 (PST) Subject: Re: [LSF/MM ATTEND][LSF/MM TOPIC] Address range mirroring enhancement References: From: Balbir Singh Message-ID: <56D3D0BA.6040209@gmail.com> Date: Mon, 29 Feb 2016 16:01:46 +1100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: "Izumi, Taku" , "lsf-pc@lists.linux-foundation.org" , "linux-mm@kvack.org" Cc: Tony Luck , Xishi Qiu On 29/02/16 13:12, Izumi, Taku wrote: > Hi, > > I'd like to atten LSF/MM 2016 and I'd like to discuss "Address range mirroring" topic. > The current status of Address range mirroring in Linux is: > - bootmem will be allocated from mirroring range > - kernel memorry will be allocated from mirroring range > by specifying kernelcore=mirror > > I think we can enhance Adderss range mirroring more. > For excample, > - The handling of mirrored memory exhaustion case > - The option any user memory can be allocated from mirrored memory > and so on. > > I'd like to discuss this topic. > > Sounds interesting! Do you have a detailed write up on the topic? Balbir Singh. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ig0-f177.google.com (mail-ig0-f177.google.com [209.85.213.177]) by kanga.kvack.org (Postfix) with ESMTP id 540756B0009 for ; Wed, 2 Mar 2016 00:31:33 -0500 (EST) Received: by mail-ig0-f177.google.com with SMTP id z8so35053402ige.0 for ; Tue, 01 Mar 2016 21:31:33 -0800 (PST) Received: from mgwkm03.jp.fujitsu.com (mgwkm03.jp.fujitsu.com. [202.219.69.170]) by mx.google.com with ESMTPS id n14si24045473ioe.193.2016.03.01.21.31.32 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Mar 2016 21:31:32 -0800 (PST) Received: from g01jpfmpwyt02.exch.g01.fujitsu.local (g01jpfmpwyt02.exch.g01.fujitsu.local [10.128.193.56]) by kw-mxq.gw.nic.fujitsu.com (Postfix) with ESMTP id AEAEEAC030D for ; Wed, 2 Mar 2016 14:31:24 +0900 (JST) From: "Izumi, Taku" Subject: RE: [LSF/MM ATTEND][LSF/MM TOPIC] Address range mirroring enhancement Date: Wed, 2 Mar 2016 05:31:23 +0000 Message-ID: References: <56D3D0BA.6040209@gmail.com> In-Reply-To: <56D3D0BA.6040209@gmail.com> Content-Language: ja-JP Content-Type: text/plain; charset="iso-2022-jp" MIME-Version: 1.0 Sender: owner-linux-mm@kvack.org List-ID: To: Balbir Singh Cc: Tony Luck , Xishi Qiu , "lsf-pc@lists.linux-foundation.org" , "linux-mm@kvack.org" > > Hi, > > > > I'd like to atten LSF/MM 2016 and I'd like to discuss "Address range mirroring" topic. > > The current status of Address range mirroring in Linux is: > > - bootmem will be allocated from mirroring range > > - kernel memorry will be allocated from mirroring range > > by specifying kernelcore=mirror > > > > I think we can enhance Adderss range mirroring more. > > For excample, > > - The handling of mirrored memory exhaustion case > > - The option any user memory can be allocated from mirrored memory > > and so on. > > > > I'd like to discuss this topic. > > > > > > Sounds interesting! Do you have a detailed write up on the topic? Give me some time to make a detailed write up. Former discussions are: http://thread.gmane.org/gmane.linux.kernel/1884223 https://lkml.org/lkml/2015/6/4/359 http://www.mail-archive.com/linux-kernel%40vger.kernel.org/msg992524.html http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg997069.html https://lkml.org/lkml/2015/11/27/18 https://lkml.org/lkml/2015/12/8/836 Sincerely, Taku Izumi > > Balbir Singh. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f71.google.com (mail-pa0-f71.google.com [209.85.220.71]) by kanga.kvack.org (Postfix) with ESMTP id 1465C6B0005 for ; Fri, 29 Apr 2016 11:57:44 -0400 (EDT) Received: by mail-pa0-f71.google.com with SMTP id zy2so175750261pac.1 for ; Fri, 29 Apr 2016 08:57:44 -0700 (PDT) Received: from mga09.intel.com (mga09.intel.com. [134.134.136.24]) by mx.google.com with ESMTP id ul1si311411pab.19.2016.04.29.08.57.43 for ; Fri, 29 Apr 2016 08:57:43 -0700 (PDT) From: Dave Hansen Subject: Re: [LSF/MM ATTEND][LSF/MM TOPIC] Address range mirroring enhancement References: <56D3D0BA.6040209@gmail.com> Message-ID: <57238476.5050505@intel.com> Date: Fri, 29 Apr 2016 08:57:42 -0700 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: "Izumi, Taku" , Balbir Singh Cc: Tony Luck , Xishi Qiu , "lsf-pc@lists.linux-foundation.org" , "linux-mm@kvack.org" , "Kleen, Andi" , "Shutemov, Kirill" , Mel Gorman On 03/01/2016 09:31 PM, Izumi, Taku wrote: >> > > I'd like to atten LSF/MM 2016 and I'd like to discuss "Address range mirroring" topic. >> > > The current status of Address range mirroring in Linux is: >> > > - bootmem will be allocated from mirroring range >> > > - kernel memorry will be allocated from mirroring range >> > > by specifying kernelcore=mirror >> > > >> > > I think we can enhance Adderss range mirroring more. >> > > For excample, >> > > - The handling of mirrored memory exhaustion case >> > > - The option any user memory can be allocated from mirrored memory >> > > and so on. It sounds like there was some good discussions of this at LSF/MM: https://lwn.net/Articles/684866/ One thing I wanted to add: There's an Intel platform (Knights Landing aka Xeon Phi) that has some on-package memory. It's higher-bandwidth than normal DRAM, but it shows up as a really slow, remote NUMA node. Instead of needing to come up with new syscalls for allocating from this new memory, applications just use the plain old NUMA APIs. While this doesn't help any of the other issues for mirroring (the fallback and exhaustion problems), is there a reason we shouldn't use the NUMA APIs for this? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org