Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1683022

Re: [PATCH 2/2] mm, memory_hotplug: remove zone restrictions

From Wei Yang <richard.weiyang@gmail.com>
Newsgroups linux.kernel
Subject Re: [PATCH 2/2] mm, memory_hotplug: remove zone restrictions
Date 2017-07-07 10:40 +0200
Message-ID <u0wXT-1kR-5@gated-at.bofh.it> (permalink)
References (4 earlier) <tY0IN-3Mu-17@gated-at.bofh.it> <tY0Su-3QH-13@gated-at.bofh.it> <tY1Yd-4JJ-5@gated-at.bofh.it> <u01Kq-4tO-13@gated-at.bofh.it> <u08Vz-Sf-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Thu, Jul 06, 2017 at 08:56:50AM +0200, Michal Hocko wrote:
>> Below is a result with a little changed kernel to show the start_pfn always.
>> The sequence is:
>> 1. bootup
>> 
>> Node 0, zone  Movable
>>         spanned  65536
>> 	present  0
>> 	managed  0
>>   start_pfn:           0
>> 
>> 2. online movable 2 continuous memory_blocks
>> 
>> Node 0, zone  Movable
>>         spanned  65536
>> 	present  65536
>> 	managed  65536
>>   start_pfn:           1310720
>> 
>> 3. offline 2nd memory_blocks
>> 
>> Node 0, zone  Movable
>>         spanned  65536
>> 	present  32768
>> 	managed  32768
>>   start_pfn:           1310720
>> 
>> 4. offline 1st memory_blocks
>> 
>> Node 0, zone  Movable
>>         spanned  65536
>> 	present  0
>> 	managed  0
>>   start_pfn:           1310720
>> 
>> So I am not sure this is still clearly defined?
>
>Could you be more specific what is not clearly defined? You have
>offlined all online memory blocks so present/managed is 0 while the
>spanned is unchanged because the zone is still defined in range
>[1310720, 1376256].
>

The zone is empty after remove these two memory blocks, while we still think
it is defined in range [1310720, 1376256]. This is what I want to point.

>I also do not see how this is related with the discussed patch as there
>is no zone interleaving involved.

I had a patch which fix the behavior, which means we can make sure the zone is
empty after remove these two memory blocks. As you mentioned in the reply,
http://www.spinics.net/lists/linux-mm/msg130230.html, I thought you would have
this fixed in this cycle. While it looks we will still have this behavior in
this cycle and looks no intend to fix this?

>-- 
>Michal Hocko
>SUSE Labs

-- 
Wei Yang
Help you, Help me

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: [PATCH 2/2] mm, memory_hotplug: remove zone restrictions Wei Yang <richard.weiyang@gmail.com> - 2017-07-06 01:20 +0200
  Re: [PATCH 2/2] mm, memory_hotplug: remove zone restrictions Michal Hocko <mhocko@kernel.org> - 2017-07-06 09:00 +0200
    Re: [PATCH 2/2] mm, memory_hotplug: remove zone restrictions Wei Yang <richard.weiyang@gmail.com> - 2017-07-07 10:40 +0200
      Re: [PATCH 2/2] mm, memory_hotplug: remove zone restrictions Michal Hocko <mhocko@kernel.org> - 2017-07-07 14:50 +0200

csiph-web