From patchwork Fri Oct 25 01:22:57 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Shakeel Butt X-Patchwork-Id: 13849916 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id DB205D1038E for ; Fri, 25 Oct 2024 01:23:29 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 5657E6B0099; Thu, 24 Oct 2024 21:23:29 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 514C86B009B; Thu, 24 Oct 2024 21:23:29 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 404D66B009C; Thu, 24 Oct 2024 21:23:29 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id 1FDCC6B0099 for ; Thu, 24 Oct 2024 21:23:29 -0400 (EDT) Received: from smtpin09.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id 41D84802D4 for ; Fri, 25 Oct 2024 01:23:12 +0000 (UTC) X-FDA: 82710375888.09.93D6579 Received: from out-176.mta0.migadu.com (out-176.mta0.migadu.com [91.218.175.176]) by imf28.hostedemail.com (Postfix) with ESMTP id E1714C001E for ; Fri, 25 Oct 2024 01:23:07 +0000 (UTC) Authentication-Results: imf28.hostedemail.com; dkim=pass header.d=linux.dev header.s=key1 header.b=q3drv2SM; spf=pass (imf28.hostedemail.com: domain of shakeel.butt@linux.dev designates 91.218.175.176 as permitted sender) smtp.mailfrom=shakeel.butt@linux.dev; dmarc=pass (policy=none) header.from=linux.dev ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1729819254; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-transfer-encoding:content-transfer-encoding: in-reply-to:references:dkim-signature; bh=C0UraTOk35e4AElBVGDH4f7gupo0690G0MiExShjFXI=; b=ciuAxHmuhUx4q3lx61bgCq2uWBCew8V69M5O6OpDd5oRJPWwY0k61NskpvStLqcfDDF9KH spwUgez8WmzXxYtNV2cyKzXuA1iN2tqL8U8rC5IibUe20PpGy0W2tiQRGHMc1Iv+7JWC38 iFwZ2NCzVTJTtWTQ6Ch1Njej1s5LmwM= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1729819254; a=rsa-sha256; cv=none; b=b6okn/+yM1D5Vl8kQ97yuh1s5vxYxMv8Fuq0+XoUZx/OWJ8b5B2DeKjttS4Dj/Jx9CtlB5 c70CkTFIKk7LN7wj5hq75Ic/5CDzVK56Csni2mlSQErgIHTvo0rI34YFjZ5TpaDVy06P4h x3L1ps6aNQcrrI2R1qagFvJnmta3DF8= ARC-Authentication-Results: i=1; imf28.hostedemail.com; dkim=pass header.d=linux.dev header.s=key1 header.b=q3drv2SM; spf=pass (imf28.hostedemail.com: domain of shakeel.butt@linux.dev designates 91.218.175.176 as permitted sender) smtp.mailfrom=shakeel.butt@linux.dev; dmarc=pass (policy=none) header.from=linux.dev X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1729819405; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=C0UraTOk35e4AElBVGDH4f7gupo0690G0MiExShjFXI=; b=q3drv2SMSDDq+5iNa1kyRlCdabxBwgswqn/pkL3XoD+0ZmVo4QkCRnAtGljj8xiqdXVZ1k SCaryAAwPXlknWjndB6ps+rIOUc2X/xUmbhvRzvV6mAeOMqlqQzR2cejsaP7dgrdbSeYQA zGDaXbzCY7Ld+3S2qOGVHP1WR7ma/OY= From: Shakeel Butt To: Andrew Morton Cc: Johannes Weiner , Michal Hocko , Roman Gushchin , Muchun Song , Hugh Dickins , Yosry Ahmed , linux-mm@kvack.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org, Meta kernel team Subject: [PATCH v1 0/6] memcg-v1: fully deprecate charge moving Date: Thu, 24 Oct 2024 18:22:57 -0700 Message-ID: <20241025012304.2473312-1-shakeel.butt@linux.dev> MIME-Version: 1.0 X-Migadu-Flow: FLOW_OUT X-Rspamd-Queue-Id: E1714C001E X-Stat-Signature: nhyozmisn9m5pyug7hpfsarg8cgf8zpa X-Rspamd-Server: rspam09 X-Rspam-User: X-HE-Tag: 1729819387-175919 X-HE-Meta: U2FsdGVkX1+RtqtA4u+w39eZakqdCDXbb/WJXfLWOH39Rq+wVHCeggHoxxY7UHV40tb4roWxHiiimCl2qjxNGgGAld9LXiHMPI5FNe7af6WXAe2iuiRRVPsehI9e+IMc8XNzyL+lpth7/yPzIpVWBiKTAAbYowM/DCiZpGch5aXjAZagnOPGDUKQjYF/A4DNsqVkqRyjvbOsqY+We+MWoarYXu3PZ+SVTp2tiXyXqBLuawkhy1nCvfoZ8pI91eKgdePjSvgkJpPDLbx/LoXzLwJxXrqSzgfWSQ0fpoP1goKfhlgWQsGiGDdULoqPDebIV7t5jgstVPWGfNE3FKmk4+LnVowSWyJRJYcUeq+uO4zmj/kamjII/kPf4SsMQ+DBVxhOeZBzX1ysFYjrOqf6Ltvh9WrgnM8lKDsbS6E3tcFovVlrlhw/lX5vsqg3BKnO7ribKDfp3f3bMZnNGYpeKeunpAx2WVvr9XUGom2WtE/7zaOVTpo2Ntm8FMaUkL4jvuJfjCF8hOfrsHIQ4++jkY247YweqbhtUnoj2F5boh3XdPYpBvePjWoicuUf8z4UHOXB3DmF3tMfp5Ww4wVz5kuk8sxA0qLODH6/YSnH6DecVc7KMcSWfPEWf/Z/naOEEhoyBI4T2nWIneV+ehPYJQK4STGeNSDa2VSHjuTVDnQJrINxLnGKuzQ+8U814lLsfjUfTFHtqASC3OZK6rOcVu0dUw6LT2lSrDSPofChRlgwnaCGAl4eSPVLdzS7wWC9KNfVQKRdjbxpz6wzdaaqMx0b2kqFch0j+Va4Qxyb7ky6iKTeJVWJnkuhZMkuOUyjobJbLwkSjwu4qrlCO4nkS8SMIe0wUs2uagAc9VManWhVVRj9qBWExPft7u/zoHMRPTb1I3cfm4H3zxGS0b/P13I8pkfGk2/w5QjWOQAXuc7j5Wfc/0i+nLGUzW8JhxrGgfT8Ng6YNVoWcduCUMu b/HMsaST XLvoJY/qXCQjBOzatwLoqpTTkQsBxxCcq6clgVVE0Jcc5o7ZHikYFn29wu8OR8Yk5JGewQg0XOy8wmVnss0HSGMAbu2HycFBSvY4oDSmie/qCXs2jJ/MQtz6vEaocS7T21j62HPhJeWGPFls= X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: The memcg v1's charge moving feature has been deprecated for almost 2 years and the kernel warns if someone try to use it. This warning has been backported to all stable kernel and there have not been any report of the warning or the request to support this feature anymore. Let's proceed to fully deprecate this feature. Changes since RFC: - Writing 0 to memory.move_charge_at_immigrate is allowed. - Remove the memcg move locking in separate patches. Shakeel Butt (6): memcg-v1: fully deprecate move_charge_at_immigrate memcg-v1: remove charge move code memcg-v1: no need for memcg locking for dirty tracking memcg-v1: no need for memcg locking for writeback tracking memcg-v1: no need for memcg locking for MGLRU memcg-v1: remove memcg move locking code .../admin-guide/cgroup-v1/memory.rst | 82 +- fs/buffer.c | 5 - include/linux/memcontrol.h | 59 -- mm/filemap.c | 1 - mm/memcontrol-v1.c | 958 +----------------- mm/memcontrol-v1.h | 6 - mm/memcontrol.c | 14 - mm/page-writeback.c | 20 +- mm/rmap.c | 1 - mm/vmscan.c | 11 - 10 files changed, 8 insertions(+), 1149 deletions(-)