From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f199.google.com (mail-pf0-f199.google.com [209.85.192.199]) by kanga.kvack.org (Postfix) with ESMTP id 558A76B0033 for ; Mon, 23 Oct 2017 15:25:28 -0400 (EDT) Received: by mail-pf0-f199.google.com with SMTP id u27so16756153pfg.12 for ; Mon, 23 Oct 2017 12:25:28 -0700 (PDT) Received: from mga07.intel.com (mga07.intel.com. [134.134.136.100]) by mx.google.com with ESMTPS id q5si5225909pgp.196.2017.10.23.12.25.26 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Oct 2017 12:25:27 -0700 (PDT) Date: Mon, 23 Oct 2017 12:25:24 -0700 From: Sharath Kumar Bhat Subject: Re: [PATCH] mm: fix movable_node kernel command-line Message-ID: <20171023192524.GC12198@linux.intel.com> Reply-To: sharath.k.bhat@linux.intel.com References: <20171023125213.whdiev6bjxr72gow@dhcp22.suse.cz> <20171023160314.GA11853@linux.intel.com> <20171023161554.zltjcls34kr4234m@dhcp22.suse.cz> <20171023171435.GA12025@linux.intel.com> <20171023172008.kr6dzpe63nfpgps7@dhcp22.suse.cz> <20171023173544.GA12198@linux.intel.com> <20171023174905.ap4uz6puggeqnz3s@dhcp22.suse.cz> <20171023184852.GB12198@linux.intel.com> <20171023190459.odyu26rqhuja4trj@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171023190459.odyu26rqhuja4trj@dhcp22.suse.cz> Sender: owner-linux-mm@kvack.org List-ID: To: Michal Hocko Cc: Sharath Kumar Bhat , linux-mm@kvack.org, akpm@linux-foundation.org On Mon, Oct 23, 2017 at 09:04:59PM +0200, Michal Hocko wrote: > On Mon 23-10-17 11:48:52, Sharath Kumar Bhat wrote: > > On Mon, Oct 23, 2017 at 07:49:05PM +0200, Michal Hocko wrote: > [...] > > > I am really confused about your usecase then. Why do you want to make > > > non-hotplugable memory to be movable then? > > > > Lets say, > > > > The required total memory in the system which can be dynamically > > offlined/onlined, T = M + N > > > > M = movable memory in non-hotpluggable memory (say DDR in the example) > > Why do you need this memory to be on/offlineable if you cannot hotplug > it? We do not need the memory to be physcially hot added/removed. Instead we just want it to be logically offlined so that these memory blocks are no longer used by the OS which has offlined it and can be used by the second OS. Once it is done using the memory for a certain use case it can be returned back by onlining it. -- 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