From: "Kani, Toshimitsu" <toshi.kani@hpe.com>
To: "mhocko@kernel.org" <mhocko@kernel.org>
Cc: "zhenzhang.zhang@huawei.com" <zhenzhang.zhang@huawei.com>,
"tangchen@cn.fujitsu.com" <tangchen@cn.fujitsu.com>,
"arbab@linux.vnet.ibm.com" <arbab@linux.vnet.ibm.com>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"daniel.kiper@oracle.com" <daniel.kiper@oracle.com>,
"xieyisheng1@huawei.com" <xieyisheng1@huawei.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"iamjoonsoo.kim@lge.com" <iamjoonsoo.kim@lge.com>,
"qiuxishi@huawei.com" <qiuxishi@huawei.com>,
"yasu.isimatu@gmail.com" <yasu.isimatu@gmail.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"aarcange@redhat.com" <aarcange@redhat.com>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"imammedo@redhat.com" <imammedo@redhat.com>,
"rientjes@google.com" <rientjes@google.com>,
"mgorman@suse.de" <mgorman@suse.de>,
"ak@linux.intel.com" <ak@linux.intel.com>,
"slaoub@gmail.com" <slaoub@gmail.com>
Subject: Re: [RFC PATCH] rework memory hotplug onlining
Date: Thu, 16 Mar 2017 17:19:34 +0000 [thread overview]
Message-ID: <1489688018.9118.14.camel@hpe.com> (raw)
In-Reply-To: <20170316085404.GE30501@dhcp22.suse.cz>
On Thu, 2017-03-16 at 09:54 +0100, Michal Hocko wrote:
> On Wed 15-03-17 23:08:14, Kani, Toshimitsu wrote:
> > On Wed, 2017-03-15 at 10:13 +0100, Michal Hocko wrote:
:
> > > - zone = page_zone(pfn_to_page(valid_start));
> >
> > Please do not remove the fix made in a96dfddbcc043. zone needs to
> > be set from valid_start, not from start_pfn.
>
> Thanks for pointing this out. I was scratching my head about this
> part but was too tired from previous git archeology so I didn't check
> the history of this particular part.
>
> I will restore the original behavior but before I do that I am really
> curious whether partial memblocks are even supported for onlining.
> Maybe I am missing something but I do not see any explicit checks for
> NULL struct page when we set zone boundaries or online a memblock. Is
> it possible those memblocks are just never hotplugable?
check_hotplug_memory_range() checks if a given range is aligned by the
section size.
This memory device represents a memory_block, which may have multiple
sections per 'sections_per_block'. This value is set to 2GB/128MB for
2GB memory_block. So, I'd expect that hot-add works as long as the
address is aligned by 128MB, but I have not tested it myself.
Thanks,
-Toshi
next prev parent reply other threads:[~2017-03-16 17:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 9:13 [RFC PATCH] rework memory hotplug onlining Michal Hocko
2017-03-15 9:13 ` Michal Hocko
2017-03-15 10:48 ` Vitaly Kuznetsov
2017-03-15 10:48 ` Vitaly Kuznetsov
2017-03-15 12:29 ` ZONE_NORMAL vs. ZONE_MOVABLE (was: Re: [RFC PATCH] rework memory hotplug onlining) Michal Hocko
2017-03-15 12:29 ` Michal Hocko
2017-03-15 12:53 ` ZONE_NORMAL vs. ZONE_MOVABLE Vitaly Kuznetsov
2017-03-15 12:53 ` Vitaly Kuznetsov
2017-03-15 13:11 ` Michal Hocko
2017-03-15 13:11 ` Michal Hocko
2017-03-15 16:37 ` Andrea Arcangeli
2017-03-15 16:37 ` Andrea Arcangeli
2017-03-16 5:31 ` Joonsoo Kim
2017-03-16 5:31 ` Joonsoo Kim
2017-03-16 19:01 ` Andrea Arcangeli
2017-03-16 19:01 ` Andrea Arcangeli
2017-03-17 10:25 ` Igor Mammedov
2017-03-17 10:25 ` Igor Mammedov
2017-03-20 6:33 ` Joonsoo Kim
2017-03-20 6:33 ` Joonsoo Kim
2017-03-30 7:55 ` Vlastimil Babka
2017-03-30 7:55 ` Vlastimil Babka
2017-03-15 23:08 ` [RFC PATCH] rework memory hotplug onlining Kani, Toshimitsu
2017-03-16 8:54 ` Michal Hocko
2017-03-16 8:54 ` Michal Hocko
2017-03-16 17:19 ` Kani, Toshimitsu [this message]
2017-03-16 17:40 ` Michal Hocko
2017-03-16 17:40 ` Michal Hocko
2017-03-17 13:20 ` Michal Hocko
2017-03-17 13:20 ` Michal Hocko
2017-03-21 14:09 ` Dan Williams
2017-03-21 14:09 ` Dan Williams
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=1489688018.9118.14.camel@hpe.com \
--to=toshi.kani@hpe.com \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=arbab@linux.vnet.ibm.com \
--cc=daniel.kiper@oracle.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=imammedo@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=qiuxishi@huawei.com \
--cc=rientjes@google.com \
--cc=slaoub@gmail.com \
--cc=tangchen@cn.fujitsu.com \
--cc=vbabka@suse.cz \
--cc=vkuznets@redhat.com \
--cc=xieyisheng1@huawei.com \
--cc=yasu.isimatu@gmail.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 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.