From: Dave Hansen <dave.hansen@intel.com>
To: Zhang Zhen <zhenzhang.zhang@huawei.com>,
mingo@redhat.com, Yinghai Lu <yinghai@kernel.org>,
mgorman@suse.de, akpm@linux-foundation.org,
zhangyanfei@cn.fujitsu.com
Cc: wangnan0@huawei.com, Linux MM <linux-mm@kvack.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] memory-hotplug: add sysfs zone_index attribute
Date: Thu, 24 Jul 2014 10:59:51 -0700 [thread overview]
Message-ID: <53D14997.7090106@intel.com> (raw)
In-Reply-To: <53D0B8B6.8040104@huawei.com>
On 07/24/2014 12:41 AM, Zhang Zhen wrote:
> Currently memory-hotplug has two limits:
> 1. If the memory block is in ZONE_NORMAL, you can change it to
> ZONE_MOVABLE, but this memory block must be adjacent to ZONE_MOVABLE.
> 2. If the memory block is in ZONE_MOVABLE, you can change it to
> ZONE_NORMAL, but this memory block must be adjacent to ZONE_NORMAL.
>
> Without this patch, we don't know which zone a memory block is in.
> So we don't know which memory block is adjacent to ZONE_MOVABLE or
> ZONE_NORMAL.
>
> On the other hand, with this patch, we can easy to know newly added
> memory is added as ZONE_NORMAL (for powerpc, ZONE_DMA, for x86_32,
> ZONE_HIGHMEM).
A section can contain more than one zone. This interface will lie about
such sections, which is quite unfortunate.
I'd really much rather see an interface that has a section itself
enumerate to which zones it may be changed. The way you have it now,
any user has to know the rules that you've laid out above. If the
kernel changed those restrictions, we'd have to teach every application
about the change in restrictions.
--
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:[~2014-07-24 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1406187138-27911-1-git-send-email-zhenzhang.zhang@huawei.com>
2014-07-24 7:41 ` [PATCH] memory-hotplug: add sysfs zone_index attribute Zhang Zhen
2014-07-24 17:59 ` Dave Hansen [this message]
2014-07-25 2:39 ` Zhang Zhen
2014-07-25 7:19 ` Zhang Zhen
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=53D14997.7090106@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=wangnan0@huawei.com \
--cc=yinghai@kernel.org \
--cc=zhangyanfei@cn.fujitsu.com \
--cc=zhenzhang.zhang@huawei.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;
as well as URLs for NNTP newsgroup(s).