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: 13849908 Received: from out-189.mta0.migadu.com (out-189.mta0.migadu.com [91.218.175.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 16A99374EA for ; Fri, 25 Oct 2024 01:23:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.189 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1729819410; cv=none; b=fDiWr3T9vEV/iAsF2qpYUInzjSpc6EezaPxiCEJnYuZXic0Qh1qv2ems2A6moEsog376qJvQWBkH1XgiOgNRt5ANymgi9uxYVmk/TyLfHHKvuCpHvCVIAhNREGpYpv66VkvgNnVArOBBW29yovqmaiNSd2HzDY45yXWXHE/t6eE= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1729819410; c=relaxed/simple; bh=IUPcFU72Wqp5Dg1E9kEYGARjEIt5X7BWuw24f9jFEeA=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=pjCAaeXYlROLS41cpvr4exigPyYZcD+cbV2Xtrzv4NqxZhvTIJ1lHhoRtNKeApdcIWG2h1wGbqSTao87jozS2CHyqirl6KKt+372/Bt8Jn/34OXAZBiixc7S5I+X1NCrhFsesXw9ON7+6q8+rKdjEKqV4Vjm/Mjo8p+ZuBIaxhc= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=q3drv2SM; arc=none smtp.client-ip=91.218.175.189 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="q3drv2SM" 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> Precedence: bulk X-Mailing-List: linux-fsdevel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Migadu-Flow: FLOW_OUT 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(-)