Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp6794738pxb; Wed, 17 Feb 2021 13:44:35 -0800 (PST) X-Google-Smtp-Source: ABdhPJwOWZmJ9XcPaoswdOQVAjpztmSoabn+BLU3eg6WLUzz8VsXMVuGKO4Y/W0gdIHWRvahxrWb X-Received: by 2002:aa7:c351:: with SMTP id j17mr802718edr.261.1613598274995; Wed, 17 Feb 2021 13:44:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1613598274; cv=none; d=google.com; s=arc-20160816; b=OmzmAJgPVkZRS2NGTMYBk3hq5M48A0e5lvu0hzXTW1geViHq6k3x+CFDHYdhg87vUt 9yqpM1n2Cp5I30CoIgXanRMtSA+IUXAuE92tYGDw2JSsycXMvO7ZSxVUHHbNSsAZt57U 2xjb20EZ7ZxAGWkxNZBrmlWI1KR5hN4s5uEeWfoHNOkzugBADe8bujr3QMAelxdA/AF2 ALpQyyJ2Gbyzqxd3adocPQC+32otUeaVhEebiLoDR7mKOBmlP79TSEtbAAwpl9kg+3vB 2VRUsgwfDgMtFRKIYoPZzLew9mtc+pNZaUfgLWUqaViuGWV3Uxs+9cwk9IvBmPrUJDRv 0hrQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:ironport-sdr:ironport-sdr; bh=lkAOowB/KzhDX6D5NzEQSmYn0LqAlvVfnr/hJqTzqWM=; b=rNGi4V5dntZsIYOXvfHgca84mx8y3V046YaKXa1xE/9BJfEil2yJpqC827wZdReQbd Al+bnNXuFUNyZ+eUwWdAxk2F2yhF2cLloVTU8omVyHZVvAifR4+eSRCkfUusBumMKTE9 Yf4zSevHf83qYbioKHOSy/Suv0b+JMYNrnChlk8KZEMrlRWVJEmNPBapMxFtdxAN4bOT ENMNK9W+tlq+3xlpwPkkB0572YlD8IZ8FkzhOO5CQL4w/NlBJTwR9eGZehjYCVy1yKDk Hfnpm52bACrerQuMvfkLQwgV8CmNo0TrIWvBpGq/8aX2dQLLja9bhFzSnZFltGsmElPO zVlQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id m14si2160151ejn.267.2021.02.17.13.44.10; Wed, 17 Feb 2021 13:44:34 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232263AbhBQVni (ORCPT + 99 others); Wed, 17 Feb 2021 16:43:38 -0500 Received: from mga14.intel.com ([192.55.52.115]:37244 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231451AbhBQVnh (ORCPT ); Wed, 17 Feb 2021 16:43:37 -0500 IronPort-SDR: yu291xXaxY5Dor40gJOxhsgKQgZYON/6qXrTnKBr2z0cqLUPvbK5hsb7Azq86gW5AqAH5+lFKv 849pHoaOL6bQ== X-IronPort-AV: E=McAfee;i="6000,8403,9898"; a="182538747" X-IronPort-AV: E=Sophos;i="5.81,185,1610438400"; d="scan'208";a="182538747" Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Feb 2021 13:41:51 -0800 IronPort-SDR: C5zPdU0ypt0CzkHpRKqWVQAn/4XnOcOue0274V7GzSAICfx7mPoouoSEDbHqqA44qoYQTQd/kt 9ElDZzelpGGA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.81,185,1610438400"; d="scan'208";a="401430698" Received: from skl-02.jf.intel.com ([10.54.74.28]) by orsmga007.jf.intel.com with ESMTP; 17 Feb 2021 13:41:51 -0800 From: Tim Chen To: Andrew Morton , Johannes Weiner , Michal Hocko , Vladimir Davydov Cc: Tim Chen , Dave Hansen , Ying Huang , linux-mm@kvack.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 0/3] Soft limit memory management bug fixes Date: Wed, 17 Feb 2021 12:41:33 -0800 Message-Id: X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org During testing of tiered memory management based on memory soft limit, I found three issues with memory management using cgroup based soft limit in the mainline code. Fix the issues with the three patches in this series. Also updated patch 3 per Johannes' comments on the first version of this patch. Thanks. Tim Changelog: v2 1. Do soft limit tree uncharge update in batch of the same node only for v1 cgroups that have a soft limit. Batching in nodes is only relevant for cgroup v1 that has per node soft limit tree. Tim Chen (3): mm: Fix dropped memcg from mem cgroup soft limit tree mm: Force update of mem cgroup soft limit tree on usage excess mm: Fix missing mem cgroup soft limit tree updates mm/memcontrol.c | 27 +++++++++++++++++++++++---- 1 file changed, 23 insertions(+), 4 deletions(-) -- 2.20.1