linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yasuaki Ishimatsu <yasu.isimatu@gmail.com>
To: Reza Arbab <arbab@linux.vnet.ibm.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Daniel Kiper <daniel.kiper@oracle.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	Tang Chen <tangchen@cn.fujitsu.com>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	David Vrabel <david.vrabel@citrix.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>,
	David Rientjes <rientjes@google.com>,
	Andrew Banman <abanman@sgi.com>, Chen Yucong <slaoub@gmail.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Subject: Re: [PATCH 2/3] memory-hotplug: more general validation of zone during online
Date: Wed, 11 May 2016 08:17:41 -0700 (PDT)	[thread overview]
Message-ID: <57334d15.524a370a.4b1f7.fffff006@mx.google.com> (raw)
In-Reply-To: <20160510203943.GA22115@arbab-laptop.austin.ibm.com>


On Tue, 10 May 2016 15:39:43 -0500
Reza Arbab <arbab@linux.vnet.ibm.com> wrote:

> On Tue, May 10, 2016 at 11:08:56AM -0700, Yasuaki Ishimatsu wrote:
> >On Mon,  9 May 2016 12:53:38 -0500
> >Reza Arbab <arbab@linux.vnet.ibm.com> wrote:
> >> * If X is lower than Y, the onlined memory must lie at the end of X.
> >> * If X is higher than Y, the onlined memory must lie at the start of X.
> >
> >If memory address has hole, memory address gets uncotinuous. Then memory
> >cannot be changed the zone by above the two conditions. So the conditions
> >shouold be removed.
> 
> I don't understand what you mean by this. Could you give an example?

> +int zone_can_shift(unsigned long pfn, unsigned long nr_pages,
> +		   enum zone_type target)
> +{
<snip>
> +	if (idx < target) {
> +		/* pages must be at end of current zone */
> +		if (pfn + nr_pages != zone_end_pfn(zone))
> +			return 0;
<snip>
> +	if (target < idx) {
> +		/* pages must be at beginning of current zone */
> +		if (pfn != zone->zone_start_pfn)
> +			return 0;

According your patch, memory address must be continuous for changing zone.
So if memory address is uncontinuous as follows, memory address 0x180000000-0x1FFFFFFFF
can be changed from ZONE_NORMAL to ZONE_MOVABLE. But memory address 0x80000000-0xFFFFFFFF
can not be changed from ZONE_NORMAL to ZONE_MOVABLE since it does not meet
above condition.

Memory address
  0x80000000 -  0xFFFFFFFF
 0x180000000 - 0x1FFFFFFFF

Thanks,
Yasuaki Ishimatsu




--
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>

  reply	other threads:[~2016-05-11 15:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09 17:53 [PATCH 0/3] memory-hotplug: improve rezoning capability Reza Arbab
2016-05-09 17:53 ` [PATCH 1/3] memory-hotplug: add move_pfn_range() Reza Arbab
2016-05-10 16:47   ` Yasuaki Ishimatsu
2016-05-09 17:53 ` [PATCH 2/3] memory-hotplug: more general validation of zone during online Reza Arbab
2016-05-10 18:08   ` Yasuaki Ishimatsu
2016-05-10 20:39     ` Reza Arbab
2016-05-11 15:17       ` Yasuaki Ishimatsu [this message]
2016-05-11 19:23         ` Reza Arbab
2016-05-13 17:24           ` Yasuaki Ishimatsu
2016-05-13 17:26   ` Yasuaki Ishimatsu
2016-05-09 17:53 ` [PATCH 3/3] memory-hotplug: use zone_can_shift() for sysfs valid_zones attribute Reza Arbab
2016-05-13 17:38   ` Yasuaki Ishimatsu
2016-05-09 20:11 ` [PATCH 0/3] memory-hotplug: improve rezoning capability Andrew Morton
2016-05-09 20:13   ` Andrew Morton

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=57334d15.524a370a.4b1f7.fffff006@mx.google.com \
    --to=yasu.isimatu@gmail.com \
    --cc=abanman@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=arbab@linux.vnet.ibm.com \
    --cc=dan.j.williams@intel.com \
    --cc=daniel.kiper@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rientjes@google.com \
    --cc=slaoub@gmail.com \
    --cc=tangchen@cn.fujitsu.com \
    --cc=vbabka@suse.cz \
    --cc=vkuznets@redhat.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