mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miaohe Lin <linmiaohe@huawei.com>
To: "Huang, Ying" <ying.huang@intel.com>,
	Wei Yang <richard.weiyang@gmail.com>
Cc: <akpm@linux-foundation.org>, <linux-mm@kvack.org>,
	<linux-kernel@vger.kernel.org>, <mgorman@techsingularity.net>
Subject: Re: [PATCH 2/2] mm/vmscan: make sure wakeup_kswapd with managed zone
Date: Mon, 28 Mar 2022 15:23:49 +0800	[thread overview]
Message-ID: <8ff6f619-e04a-d785-fa9a-6822c04d4ee1@huawei.com> (raw)
In-Reply-To: <8735j2opd9.fsf@yhuang6-desk2.ccr.corp.intel.com>

On 2022/3/28 9:08, Huang, Ying wrote:
> Hi, Wei,
> 
> Wei Yang <richard.weiyang@gmail.com> writes:
> 
>> wakeup_kswapd() only wake up kswapd when the zone is managed.
>>
>> For two callers of wakeup_kswapd(), they are node perspective.
>>
>>   * wake_all_kswapds
>>   * numamigrate_isolate_page
>>
>> If we picked up a !managed zone, this is not we expected.
>>
>> This patch makes sure we pick up a managed zone for wakeup_kswapd().
>>
>> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
>> ---
>>  mm/migrate.c    | 2 +-
>>  mm/page_alloc.c | 2 ++
>>  2 files changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/mm/migrate.c b/mm/migrate.c
>> index 3d60823afd2d..c4b654c0bdf0 100644
>> --- a/mm/migrate.c
>> +++ b/mm/migrate.c
>> @@ -2046,7 +2046,7 @@ static int numamigrate_isolate_page(pg_data_t *pgdat, struct page *page)
>>  		if (!(sysctl_numa_balancing_mode & NUMA_BALANCING_MEMORY_TIERING))
>>  			return 0;
>>  		for (z = pgdat->nr_zones - 1; z >= 0; z--) {
>> -			if (populated_zone(pgdat->node_zones + z))
>> +			if (managed_zone(pgdat->node_zones + z))
> 
> This looks good to me!  Thanks!  It seems that we can replace
> populated_zone() in migrate_balanced_pgdat() too.  Right?

This patch looks good to me too. Thanks!

BTW: This makes me remember the bewilderment when I read the relevant code.
It's very kind of you if you could tell me the difference between
managed_zone and populated_zone. IIUC, when the caller relies on the
activity from buddy system, managed_zone should always be used. I think
there're many places like compaction need to use managed_zone but
populated_zone is used now. They might need to change to use managed_zone
too. Or am I miss something?

Many Thanks. :)

> 
>>  				break;
>>  		}
>>  		wakeup_kswapd(pgdat->node_zones + z, 0, order, ZONE_MOVABLE);
>> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
>> index 4c0c4ef94ba0..6656c2d06e01 100644
>> --- a/mm/page_alloc.c
>> +++ b/mm/page_alloc.c
>> @@ -4674,6 +4674,8 @@ static void wake_all_kswapds(unsigned int order, gfp_t gfp_mask,
>>  
>>  	for_each_zone_zonelist_nodemask(zone, z, ac->zonelist, highest_zoneidx,
>>  					ac->nodemask) {
>> +		if (!managed_zone(zone))
>> +			continue;
>>  		if (last_pgdat != zone->zone_pgdat)
>>  			wakeup_kswapd(zone, gfp_mask, order, highest_zoneidx);
>>  		last_pgdat = zone->zone_pgdat;
> 
> Best Regards,
> Huang, Ying
> 
> .
> 


  reply	other threads:[~2022-03-28  7:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-27  2:41 [PATCH 1/2] mm/vmscan: reclaim only affects managed_zones Wei Yang
2022-03-27  2:41 ` [PATCH 2/2] mm/vmscan: make sure wakeup_kswapd with managed zone Wei Yang
2022-03-28  1:08   ` Huang, Ying
2022-03-28  7:23     ` Miaohe Lin [this message]
2022-03-29  0:45       ` Wei Yang
2022-03-29  1:55         ` Miaohe Lin
2022-03-29  0:41     ` Wei Yang
2022-03-29  0:43       ` Huang, Ying
2022-03-29  1:52         ` Wei Yang
2022-03-29  2:05           ` Huang, Ying
2022-03-30  0:14             ` Wei Yang
2022-03-29  2:22           ` Matthew Wilcox
2022-03-29 23:59             ` Wei Yang
2022-03-28  7:11 ` [PATCH 1/2] mm/vmscan: reclaim only affects managed_zones Miaohe Lin
2022-03-28  7:33 ` David Hildenbrand
2022-03-28  8:14 ` Oscar Salvador
2022-03-29  0:48   ` Wei Yang

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=8ff6f619-e04a-d785-fa9a-6822c04d4ee1@huawei.com \
    --to=linmiaohe@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=richard.weiyang@gmail.com \
    --cc=ying.huang@intel.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

all inboxes | Powered by JetHome®