linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Chen <tim.c.chen@linux.intel.com>
To: Michal Hocko <mhocko@suse.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Vladimir Davydov <vdavydov.dev@gmail.com>,
	Dave Hansen <dave.hansen@intel.com>,
	Ying Huang <ying.huang@intel.com>,
	linux-mm@kvack.org, cgroups@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] mm: Fix dropped memcg from mem cgroup soft limit tree
Date: Thu, 4 Mar 2021 09:35:08 -0800	[thread overview]
Message-ID: <72cb8618-73af-ce08-d5d5-30cab30755a3@linux.intel.com> (raw)
In-Reply-To: <YC68Xo9+R2msn/ul@dhcp22.suse.cz>



On 2/18/21 11:13 AM, Michal Hocko wrote:

> 
> Fixes: 4e41695356fb ("memory controller: soft limit reclaim on contention")
> Acked-by: Michal Hocko <mhocko@suse.com>
> 
> Thanks!
>> ---
>>  mm/memcontrol.c | 6 +++++-
>>  1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
>> index ed5cc78a8dbf..a51bf90732cb 100644
>> --- a/mm/memcontrol.c
>> +++ b/mm/memcontrol.c
>> @@ -3505,8 +3505,12 @@ unsigned long mem_cgroup_soft_limit_reclaim(pg_data_t *pgdat, int order,
>>  			loop > MEM_CGROUP_MAX_SOFT_LIMIT_RECLAIM_LOOPS))
>>  			break;
>>  	} while (!nr_reclaimed);
>> -	if (next_mz)
>> +	if (next_mz) {
>> +		spin_lock_irq(&mctz->lock);
>> +		__mem_cgroup_insert_exceeded(next_mz, mctz, excess);
>> +		spin_unlock_irq(&mctz->lock);
>>  		css_put(&next_mz->memcg->css);
>> +	}
>>  	return nr_reclaimed;
>>  }
>>  
>> -- 
>> 2.20.1
> 

Mel,

Reviewing this patch a bit more, I realize that there is a chance that the removed
next_mz could be inserted back to the tree from a memcg_check_events
that happen in between.  So we need to make sure that the next_mz
is indeed off the tree and update the excess value before adding it
back.  Update the patch to the patch below.

Thanks.

Tim
---

From 412764d1fad219b04c77bcb1cc8161067c8424f2 Mon Sep 17 00:00:00 2001
From: Tim Chen <tim.c.chen@linux.intel.com>
Date: Tue, 2 Feb 2021 15:53:21 -0800
Subject: [PATCH v3] mm: Fix dropped memcg from mem cgroup soft limit tree
To: Andrew Morton <akpm@linux-foundation.org>, Johannes Weiner <hannes@cmpxchg.org>, Michal Hocko <mhocko@suse.cz>,Vladimir Davydov <vdavydov.dev@gmail.com>
Cc: Dave Hansen <dave.hansen@intel.com>, Ying Huang <ying.huang@intel.com>, linux-mm@kvack.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org

During soft limit memory reclaim, we will temporarily remove the target
mem cgroup from the cgroup soft limit tree.  We then perform memory
reclaim, update the memory usage excess count and re-insert the mem
cgroup back into the mem cgroup soft limit tree according to the new
memory usage excess count.

However, when memory reclaim failed for a maximum number of attempts
and we bail out of the reclaim loop, we forgot to put the target mem
cgroup chosen for next reclaim back to the soft limit tree. This prevented
pages in the mem cgroup from being reclaimed in the future even though
the mem cgroup exceeded its soft limit.  Fix the logic and put the mem
cgroup back on the tree when page reclaim failed for the mem cgroup.

Fixes: 4e41695356fb ("memory controller: soft limit reclaim on contention")
---
 mm/memcontrol.c | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index ed5cc78a8dbf..bc9cc73ff66b 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -3505,8 +3505,18 @@ unsigned long mem_cgroup_soft_limit_reclaim(pg_data_t *pgdat, int order,
 			loop > MEM_CGROUP_MAX_SOFT_LIMIT_RECLAIM_LOOPS))
 			break;
 	} while (!nr_reclaimed);
-	if (next_mz)
+	if (next_mz) {
+		/*
+		 * next_mz was removed in __mem_cgroup_largest_soft_limit_node.
+		 * Put it back in tree with latest excess value.
+		 */
+		spin_lock_irq(&mctz->lock);
+		__mem_cgroup_remove_exceeded(next_mz, mctz);
+		excess = soft_limit_excess(next_mz->memcg);
+		__mem_cgroup_insert_exceeded(next_mz, mctz, excess);
+		spin_unlock_irq(&mctz->lock);
 		css_put(&next_mz->memcg->css);
+	}
 	return nr_reclaimed;
 }
 
-- 
2.20.1


  reply	other threads:[~2021-03-04 17:38 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-17 20:41 [PATCH v2 0/3] Soft limit memory management bug fixes Tim Chen
2021-02-17 20:41 ` [PATCH v2 1/3] mm: Fix dropped memcg from mem cgroup soft limit tree Tim Chen
2021-02-18  8:24   ` Michal Hocko
2021-02-18 18:30     ` Tim Chen
2021-02-18 19:13       ` Michal Hocko
2021-02-18 19:51         ` Tim Chen
2021-02-18 19:13   ` Michal Hocko
2021-03-04 17:35     ` Tim Chen [this message]
2021-03-05  9:11       ` Michal Hocko
2021-03-05 19:07         ` Tim Chen
2021-03-08  8:34           ` Michal Hocko
2021-02-17 20:41 ` [PATCH v2 2/3] mm: Force update of mem cgroup soft limit tree on usage excess Tim Chen
2021-02-19  9:11   ` Michal Hocko
2021-02-19 18:59     ` Tim Chen
2021-02-20 16:23       ` Tim Chen
2021-02-22  8:40       ` Michal Hocko
2021-02-22 17:41         ` Tim Chen
2021-02-22 19:09           ` Michal Hocko
2021-02-22 19:23             ` Tim Chen
2021-02-22 19:48             ` Tim Chen
2021-02-24 11:53               ` Michal Hocko
2021-02-25 22:48                 ` Tim Chen
2021-02-26  8:52                   ` Michal Hocko
2021-02-27  0:56                     ` Tim Chen
2021-03-01  7:39                       ` Michal Hocko
2021-02-25 22:25           ` Tim Chen
2021-03-02  6:25   ` [mm] 4f09feb8bf: vm-scalability.throughput -4.3% regression kernel test robot
2021-02-17 20:41 ` [PATCH v2 3/3] mm: Fix missing mem cgroup soft limit tree updates Tim Chen
2021-02-18  5:56   ` Johannes Weiner
2021-02-22 18:38     ` Tim Chen
2021-02-23 15:18       ` Johannes Weiner
2021-02-19  9:16   ` Michal Hocko
2021-02-19 19:28     ` Tim Chen
2021-02-22  8:41       ` Michal Hocko
2021-02-22 17:45         ` Tim Chen

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=72cb8618-73af-ce08-d5d5-30cab30755a3@linux.intel.com \
    --to=tim.c.chen@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=dave.hansen@intel.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=vdavydov.dev@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;
as well as URLs for NNTP newsgroup(s).