Re: [PATCH] mm: fix movable_node kernel command-line

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]
  Powered by Linux