linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Michal Hocko <mhocko@kernel.org>, Wei Yang <richard.weiyang@gmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/memory_hotplug: just build zonelist for new added node
Date: Wed, 28 Jun 2017 11:35:00 +0200	[thread overview]
Message-ID: <f92958f9-e831-8dc7-f8e6-2f4a46171e71@suse.cz> (raw)
In-Reply-To: <20170628092329.GC5225@dhcp22.suse.cz>

On 06/28/2017 11:23 AM, Michal Hocko wrote:
> On Mon 26-06-17 11:58:22, Wei Yang wrote:
>> In commit (9adb62a5df9c0fbef7) "mm/hotplug: correctly setup fallback
>> zonelists when creating new pgdat" tries to build the correct zonelist for
>> a new added node, while it is not necessary to rebuild it for already exist
>> nodes.
>>
>> In build_zonelists(), it will iterate on nodes with memory. For a new added
>> node, it will have memory until node_states_set_node() is called in
>> online_pages().
>>
>> This patch will avoid to rebuild the zonelists for already exist nodes.
> 
> It is not very clear from the changelog why that actually matters. The
> only effect I can see is that other zonelists on other online nodes will
> not learn about the currently memory less node. This is a good think
> because we do not pointlessly try to allocate from that node.

build_zonelists_node() seems to use managed_zone(zone) checks, so it
should not include empty zones anyway. So effectively seems to me we
just avoid some pointless work under stop_machine().

>> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
> 
> Acked-by: Michal Hocko <mhocko@suse.com>
> 
>> ---
>>  mm/page_alloc.c | 16 +++++++++-------
>>  1 file changed, 9 insertions(+), 7 deletions(-)
>>
>> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
>> index 560eafe8234d..fc8181b44fd8 100644
>> --- a/mm/page_alloc.c
>> +++ b/mm/page_alloc.c
>> @@ -5200,15 +5200,17 @@ static int __build_all_zonelists(void *data)
>>  	memset(node_load, 0, sizeof(node_load));
>>  #endif
>>  
>> -	if (self && !node_online(self->node_id)) {
>> +	/* This node is hotadded and no memory preset yet.
>> +	 * So just build zonelists is fine, no need to touch other nodes.
>> +	 */
> 
> This comment doesn't make much sense to me. What about
> 	/*
> 	 * Do not rebuild zonelists on all online nodes if the current
> 	 * node is not online yet (it doesn't have any memory) and
> 	 * allocating from it is pointless. Still build zonelist for
> 	 * self because we need to handle memoryless nodes.
> 	 */
>> +	if (self && !node_online(self->node_id))
>>  		build_zonelists(self);
>> -	}
>> -
>> -	for_each_online_node(nid) {
>> -		pg_data_t *pgdat = NODE_DATA(nid);
>> +	else
>> +		for_each_online_node(nid) {
>> +			pg_data_t *pgdat = NODE_DATA(nid);
>>  
>> -		build_zonelists(pgdat);
>> -	}
>> +			build_zonelists(pgdat);
>> +		}
>>  
>>  	/*
>>  	 * Initialize the boot_pagesets that are going to be used
>> -- 
>> 2.11.0
>>
>> --
>> 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>
> 

--
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:[~2017-06-28  9:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26  3:58 Wei Yang
2017-06-28  7:06 ` Vlastimil Babka
2017-06-28  7:28   ` Wei Yang
2017-06-28  9:23 ` Michal Hocko
2017-06-28  9:35   ` Vlastimil Babka [this message]
2017-06-28  9:45     ` Michal Hocko

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=f92958f9-e831-8dc7-f8e6-2f4a46171e71@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=richard.weiyang@gmail.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