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 337C5C64990 for ; Thu, 25 Aug 2022 13:35:06 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 8B7EB6B0073; Thu, 25 Aug 2022 09:35:05 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 86793940008; Thu, 25 Aug 2022 09:35:05 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 708B9940007; Thu, 25 Aug 2022 09:35:05 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0010.hostedemail.com [216.40.44.10]) by kanga.kvack.org (Postfix) with ESMTP id 613FB6B0073 for ; Thu, 25 Aug 2022 09:35:05 -0400 (EDT) Received: from smtpin30.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay03.hostedemail.com (Postfix) with ESMTP id 467BEA1B96 for ; Thu, 25 Aug 2022 13:35:05 +0000 (UTC) X-FDA: 79838210970.30.6FB1CA7 Received: from mail-ej1-f42.google.com (mail-ej1-f42.google.com [209.85.218.42]) by imf25.hostedemail.com (Postfix) with ESMTP id 69426A0006 for ; Thu, 25 Aug 2022 13:35:03 +0000 (UTC) Received: by mail-ej1-f42.google.com with SMTP id v14so3042149ejf.9 for ; Thu, 25 Aug 2022 06:35:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cmpxchg-org.20210112.gappssmtp.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc; bh=maHy+RdG1bfZFcMYc9WoBOBgcyZgJzrvT/br9of5/VU=; b=ki59yMmI7FCk8x3aODpep64NKP8t1/4KYxMTUMMmwXZzS7FTFF7NyXtV3OQEzwBO8i ixy2Ie3yBDN6MY9J6oh5ohKreOhyo4exnqAFtyDKyGIlmMEoYYKv5UvuVW3BpzpK3A8u A+7XL429LMEIxpIIwyJTOz0NA8se0/inNDugUuas2ut7vqjWuB5zrL1DUwzw8tv87ahu 2nJ5bjWNidheTYWOAkK5DgmkK9F9z7cyBalUhH9epPhy73xf2ROJwaJA5xylPX1yvZrl l+q1P0cdFMUVBHTnZXGgW0s8vq3N5rLVszPhTP+7mm1iaK128FV3V6UVbyj1gmG9ENDu JRJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc; bh=maHy+RdG1bfZFcMYc9WoBOBgcyZgJzrvT/br9of5/VU=; b=j0/e6IFrm8AZVZ3ri0uPWwUcdiDp5NinQUxr3y3Sse+48PnhwzlvH3ok7IBVV5M8UZ s8jhk59KrMa2+M7wcGip/okyjIUWBKcL8EhXbT7YD246DsjDNLhYaLTx7733VFHilJYO VLKLZFaVMnCPp0GYNtR54cF8HpS3hIBI0GUGjbQpFoZyOfLJFtclOjf4x4WGIM/9m+p9 2Gf85wgWfEzoq8yC7a8xF4mQla0VhNxCt47mGexJ32Qihr1RPr9C8jJDd+3kLnvU0P8+ lY3QJIEiN/F4Bzp6uq+39PQULZ7yi5SMKZ0nWy0iTi2pUSn2aL0NDxE9FAP8CBEhXE8A q2EA== X-Gm-Message-State: ACgBeo1ktmt/+NtVOD05v3FPSEOWDOferznb6AZZ4bkhQvxYkgAXNC0n Wus/kHsbtsSZl3Ofd1NoUsbZGg== X-Google-Smtp-Source: AA6agR68Mc5Uo00qzU7ZBlI2Td38wWc8YYe05Y9uKw9yUI6KGPOGWg8b0eKy6paLME3n78tCMGxBlQ== X-Received: by 2002:a17:907:75d9:b0:73d:dda8:b6c with SMTP id jl25-20020a17090775d900b0073ddda80b6cmr397885ejc.319.1661434502051; Thu, 25 Aug 2022 06:35:02 -0700 (PDT) Received: from localhost (ip-109-192-149-028.um38.pools.vodafone-ip.de. [109.192.149.28]) by smtp.gmail.com with ESMTPSA id l10-20020a1709060cca00b0073bf84be798sm2501321ejh.142.2022.08.25.06.35.01 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 25 Aug 2022 06:35:01 -0700 (PDT) Date: Thu, 25 Aug 2022 09:35:00 -0400 From: Johannes Weiner To: Zhaoyang Huang Cc: Michal Hocko , Suren Baghdasaryan , Tejun Heo , Shakeel Butt , "zhaoyang.huang" , Linux MM , LKML , Cgroups , Ke Wang , Zefan Li , Roman Gushchin , Muchun Song Subject: Re: [RFC PATCH] memcg: use root_mem_cgroup when css is inherited Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ARC-Authentication-Results: i=1; imf25.hostedemail.com; dkim=pass header.d=cmpxchg-org.20210112.gappssmtp.com header.s=20210112 header.b=ki59yMmI; spf=pass (imf25.hostedemail.com: domain of hannes@cmpxchg.org designates 209.85.218.42 as permitted sender) smtp.mailfrom=hannes@cmpxchg.org; dmarc=pass (policy=none) header.from=cmpxchg.org ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1661434505; a=rsa-sha256; cv=none; b=VMBiOZyE8T41cD+KsyhZo/+X2qBkduvN5TcQuP1YxgmkPmun/xg//IxMO+5DMRVieX7kz6 LlwVlqmFvvxJN8CxIacV4zTwHm2QZa+6mVMY2rT2XJG7yf+xP4nOpdxnrNmfM5H/rMjSTP kP2KzTufhCKqZvImI+971KxJQBwI+S8= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1661434505; 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=maHy+RdG1bfZFcMYc9WoBOBgcyZgJzrvT/br9of5/VU=; b=SiAUaB7a9eKy2hCJvHkVIglxdgQwuWNYfbJ3Q86VjuiGVPt50sYLEombisWspVVPCNuR3v Fjvuch27AiANZS8tUpnkKDiTdeadGpmTyy2N9yICIemhTOEd2ANugxq27urwuoQtkz9zXG wCYte1pF/ZL9yjHm2yBxRjH5D1ARdhc= X-Rspam-User: X-Rspamd-Queue-Id: 69426A0006 X-Stat-Signature: 7m5gk3g3ddu9ge49o8h9b918jhxw658u Authentication-Results: imf25.hostedemail.com; dkim=pass header.d=cmpxchg-org.20210112.gappssmtp.com header.s=20210112 header.b=ki59yMmI; spf=pass (imf25.hostedemail.com: domain of hannes@cmpxchg.org designates 209.85.218.42 as permitted sender) smtp.mailfrom=hannes@cmpxchg.org; dmarc=pass (policy=none) header.from=cmpxchg.org X-Rspamd-Server: rspam01 X-HE-Tag: 1661434503-574738 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: On Thu, Aug 25, 2022 at 06:11:09PM +0800, Zhaoyang Huang wrote: > Sorry for any misunderstanding among the discussion. My purpose is > real and simple as I have stated from the very beginning that I would > like to have per-app cgroup hierarchy to charge memory to root if it > is not enabled explicitly for memory. The reason has also been stated > like reclaim and workingset regression in suren's report. I don't > think my proposal will do any harm to current v2's mechanism besides > asking for the admin echo "+memory" to their desire group. It would permit children to escape parental control, completely breaking the hierarchy and delegation guarantees currently in place. That just isn't going to happen. Nacked-by: Johannes Weiner I would suggest focusing on finding the root cause for the reclaim problem you are describing. It's possible all we need is a fix to reclaim or the workingset code.