From: Vlastimil Babka <vbabka@suse.cz>
To: Changsheng Liu <liuchangsheng@inspur.com>,
akpm@linux-foundation.org, isimatu.yasuaki@jp.fujitsu.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
yanxiaofeng@inspur.com, fandd@inspur.com,
Changsheng Liu <liuchangcheng@inspur.com>
Subject: Re: [PATCH V2] mm:memory hot-add: memory can not been added to movable zone
Date: Thu, 20 Aug 2015 09:44:38 +0200 [thread overview]
Message-ID: <55D58566.4040709@suse.cz> (raw)
In-Reply-To: <55D584C7.7060101@suse.cz>
On 08/20/2015 09:41 AM, Vlastimil Babka wrote:
> want to hot-remove and don't want movable zones (which limit what kind
> of allocations are possible), is there a way to prevent memory being
> movable after your patch?
Oh, and not enabling CONFIG_MOVABLE_NODE is not sufficient here IMHO, as
users might want to use a distro kernel that has the option enabled, but
still not want to use 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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Vlastimil Babka <vbabka@suse.cz>
To: Changsheng Liu <liuchangsheng@inspur.com>,
akpm@linux-foundation.org, isimatu.yasuaki@jp.fujitsu.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
yanxiaofeng@inspur.com, fandd@inspur.com,
Changsheng Liu <liuchangcheng@inspur.com>
Subject: Re: [PATCH V2] mm:memory hot-add: memory can not been added to movable zone
Date: Thu, 20 Aug 2015 09:44:38 +0200 [thread overview]
Message-ID: <55D58566.4040709@suse.cz> (raw)
In-Reply-To: <55D584C7.7060101@suse.cz>
On 08/20/2015 09:41 AM, Vlastimil Babka wrote:
> want to hot-remove and don't want movable zones (which limit what kind
> of allocations are possible), is there a way to prevent memory being
> movable after your patch?
Oh, and not enabling CONFIG_MOVABLE_NODE is not sufficient here IMHO, as
users might want to use a distro kernel that has the option enabled, but
still not want to use it.
next prev parent reply other threads:[~2015-08-20 7:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 7:28 [PATCH V2] mm:memory hot-add: memory can not been added to movable zone Changsheng Liu
2015-08-20 7:28 ` Changsheng Liu
2015-08-20 7:41 ` Vlastimil Babka
2015-08-20 7:41 ` Vlastimil Babka
2015-08-20 7:44 ` Vlastimil Babka [this message]
2015-08-20 7:44 ` Vlastimil Babka
2015-08-21 2:00 ` Changsheng Liu
2015-08-21 2:00 ` Changsheng Liu
2015-08-24 14:13 ` Vlastimil Babka
2015-08-24 14:13 ` Vlastimil Babka
2015-08-25 13:12 ` Yasuaki Ishimatsu
2015-08-25 13:12 ` Yasuaki Ishimatsu
2015-08-26 0:38 ` Changsheng Liu
2015-08-26 0:38 ` Changsheng Liu
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=55D58566.4040709@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=fandd@inspur.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuchangcheng@inspur.com \
--cc=liuchangsheng@inspur.com \
--cc=yanxiaofeng@inspur.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.