From mboxrd@z Thu Jan 1 00:00:00 1970 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 8EF16D10399 for ; Fri, 25 Oct 2024 01:33:37 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id E6B1D6B009D; Thu, 24 Oct 2024 21:33:36 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id E199B6B009F; Thu, 24 Oct 2024 21:33:36 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id CB9AD6B00A0; Thu, 24 Oct 2024 21:33:36 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0017.hostedemail.com [216.40.44.17]) by kanga.kvack.org (Postfix) with ESMTP id ACB6A6B009D for ; Thu, 24 Oct 2024 21:33:36 -0400 (EDT) Received: from smtpin19.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay03.hostedemail.com (Postfix) with ESMTP id BD5A6A018D for ; Fri, 25 Oct 2024 01:33:01 +0000 (UTC) X-FDA: 82710401592.19.DA4504E Received: from out-171.mta1.migadu.com (out-171.mta1.migadu.com [95.215.58.171]) by imf22.hostedemail.com (Postfix) with ESMTP id 187B6C001F for ; Fri, 25 Oct 2024 01:33:10 +0000 (UTC) Authentication-Results: imf22.hostedemail.com; dkim=pass header.d=linux.dev header.s=key1 header.b=RGmI6tKR; spf=pass (imf22.hostedemail.com: domain of shakeel.butt@linux.dev designates 95.215.58.171 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=1729819810; 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-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=w3cyFDDl9Fn7myhSdVnKeGIMsM9Cumy3wrd3akiTWoU=; b=FDSQ3gqkU/Z4+R2UJOlpD2jp2xHhND4BRUHyaZh8rO+TTT2226j22PeDuDn+DYh1eHEQOH M0XmhLBJ50YwTDx+XPp+UMEdS5lwR4mLu1vyIeyi39tE6ZFvHyv+Sb7274joTjb+sG/1CY BlDAofQnnMBVqayxRBlESX9z+1RgzA4= ARC-Authentication-Results: i=1; imf22.hostedemail.com; dkim=pass header.d=linux.dev header.s=key1 header.b=RGmI6tKR; spf=pass (imf22.hostedemail.com: domain of shakeel.butt@linux.dev designates 95.215.58.171 as permitted sender) smtp.mailfrom=shakeel.butt@linux.dev; dmarc=pass (policy=none) header.from=linux.dev ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1729819810; a=rsa-sha256; cv=none; b=Gw6IKcjebZStMSYLTM9MhvtGkRaqD7kS+fAByPGjq7kOyus31JbjrPXuKHuODWE+bGXyl4 3b/Ij/quDbZFznatG269+SXnHxE6Otscf7n0CW9vZEo/vYA8ppPg0Jy3+M1Xr23OexgoPQ eh7j8xANYBulnkEQmPTyPslxrtwoXEM= Date: Thu, 24 Oct 2024 18:33:26 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1729820012; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=w3cyFDDl9Fn7myhSdVnKeGIMsM9Cumy3wrd3akiTWoU=; b=RGmI6tKRO283K/VPcEyaGbgj6d6o/79ispGa/A4c/lTmtS+WTBqQ+UGcPGb4fBSRUIZgOI IFHh4PFjVOPE9ppsaV5R4c+rqgECVqvpcRuJezz78x1C3oxSTlw5XXyOok2IhVQFgvSI/7 3p7/Rl7oWOD3WDoUSn/9dk9FFc1R8b8= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. 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: Re: [PATCH v1 0/6] memcg-v1: fully deprecate charge moving Message-ID: References: <20241025012304.2473312-1-shakeel.butt@linux.dev> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20241025012304.2473312-1-shakeel.butt@linux.dev> X-Migadu-Flow: FLOW_OUT X-Rspamd-Server: rspam06 X-Rspamd-Queue-Id: 187B6C001F X-Stat-Signature: hkcgwyk6mi76kxm95yjtjxst1bed97qa X-Rspam-User: X-HE-Tag: 1729819990-330150 X-HE-Meta: U2FsdGVkX18bY0Dv1RuiSwjTrj0J7AqpVkk1CHtM296TfUCIXFmeIq2/BYe5qBpO77AmWeX90gqMifSMkZvj/ABRiNUpjP4nzbob1IVCknBSzHuMi0YjI2/cJD/P6PAkuCeXvFbZtFVlB02URnIys4Cl0wDxQ+WEbAHydLGXFZ136oy7ypG+1KoSkaAl8WrShMX8wSKiI9CSu7U39214UCL4oquHIHC2Q/ncG3nuJEeedgMz90zWcyeYlk9apQ4nysuLQYV56BWoTvPYJdJ58wY5wYXKJXocv903c3kgqf4rV2c4zI26Gq39ilO8HLOoUINEOpnSxONYQBZyuGkQmhBSouS1HWZpfw8kGtq41jITKfdMsT+M0YDRpAY0vorJwcaX+K/MXrRy9T/h2dzYfjIs3KqYBuTPXV2kxgOplUc4mqN34VvddF/UwltrHHp/QFOVYtlFKU7lU3XDtlHAJkD4MfsOLV1ZYrb1RMu7rh36OIjRgeec+lR6AGNOs/qrnl5MXPX7ylKpHmpPEFknyluSVhJFp6sy1gmBWeubaa11bnHd2H//6tOpdhV9C2ZA0Smp/bUqHtjC19T44DJ0naB9BbNGthy6QgDFViM0I7vR2dJFnxCBBovbNvm+LyqGCmPkjH8rhPMi/KdSv92xavQUby1k55WU6ae+xh27/7zJiGOSPJLu566pXKaFcdv5yH13xV23eRHp/qxIW2IS421s3I7J9Mwc1gcVis/SItWosIHGZyNLeNuoBgBAwKuqRBEuQSwDYW548bmMYKuizNUeJqQZ4zmV/rSnDYWNi4T1YwSZN4dD05yp3KNNvSt4jbUrhBfzgnQZ5hJIgdVwUHqziltF1+DEx/dvbJ5IeArrI0o2GleRm5L+KL6pWi637IcNZKZ42VeiGoWqUHkJHtfIvmaTfZxfj3tr7gBFCPeK3cfpggZYvSY6tlCcqlPIUDiM+hcw9R1CC6UM8/2 V3gk5waC dQ50ZFZ8l+zrjvy9lWeUBPZJLmeUM3kSJ+KA9U/GewKwjnkmMd03fp63YNAM7iPrD1ccY/g9Zu0wflKpk4buRAvO9PmSLr59kpGKeB9Wi9b5PiMOV2KkwQ27dwQhcrTbpWAe20kyWhX/EOhJfnFNPugc4+usBbRFVaMN1S658cQTJVmQ= 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: On Thu, Oct 24, 2024 at 06:22:57PM GMT, Shakeel Butt wrote: > 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 > Please ignore the patch at [1] as it was resent by mistake. [1] https://lore.kernel.org/linux-mm/20241024065712.1274481-4-shakeel.butt@linux.dev