From: Michal Hocko <mhocko@kernel.org>
To: Sharath Kumar Bhat <sharath.k.bhat@linux.intel.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org
Subject: Re: [PATCH] mm: fix movable_node kernel command-line
Date: Mon, 23 Oct 2017 21:04:59 +0200 [thread overview]
Message-ID: <20171023190459.odyu26rqhuja4trj@dhcp22.suse.cz> (raw)
In-Reply-To: <20171023184852.GB12198@linux.intel.com>
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?
--
Michal Hocko
SUSE Labs
--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-10-23 19:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 23:32 Sharath Kumar Bhat
2017-10-23 12:52 ` Michal Hocko
2017-10-23 16:03 ` Sharath Kumar Bhat
2017-10-23 16:15 ` Michal Hocko
2017-10-23 17:14 ` Sharath Kumar Bhat
2017-10-23 17:20 ` Michal Hocko
2017-10-23 17:35 ` Sharath Kumar Bhat
2017-10-23 17:49 ` Michal Hocko
2017-10-23 18:48 ` Sharath Kumar Bhat
2017-10-23 19:04 ` Michal Hocko [this message]
2017-10-23 19:25 ` Sharath Kumar Bhat
2017-10-23 19:35 ` Michal Hocko
2017-10-23 19:56 ` Sharath Kumar Bhat
2017-10-23 21:52 ` Dave Hansen
2017-10-24 1:06 ` Sharath Kumar Bhat
2017-10-24 7:19 ` Michal Hocko
2017-10-25 0:53 ` Sharath Kumar Bhat
2017-10-25 6:38 ` Michal Hocko
2017-10-25 22:01 ` Sharath Kumar Bhat
2017-10-26 7:36 ` Michal Hocko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171023190459.odyu26rqhuja4trj@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=sharath.k.bhat@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox