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 103B0C00140 for ; Thu, 18 Aug 2022 22:39:51 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 9D7E78E0001; Thu, 18 Aug 2022 18:39:50 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 986ED8D0002; Thu, 18 Aug 2022 18:39:50 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 827BA8E0001; Thu, 18 Aug 2022 18:39:50 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0014.hostedemail.com [216.40.44.14]) by kanga.kvack.org (Postfix) with ESMTP id 73C5F8D0002 for ; Thu, 18 Aug 2022 18:39:50 -0400 (EDT) Received: from smtpin12.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay08.hostedemail.com (Postfix) with ESMTP id 584D5142081 for ; Thu, 18 Aug 2022 22:39:50 +0000 (UTC) X-FDA: 79814182140.12.5CF59B1 Received: from mail-pj1-f45.google.com (mail-pj1-f45.google.com [209.85.216.45]) by imf02.hostedemail.com (Postfix) with ESMTP id DB1828077B for ; Thu, 18 Aug 2022 22:33:27 +0000 (UTC) Received: by mail-pj1-f45.google.com with SMTP id r15-20020a17090a1bcf00b001fabf42a11cso3192504pjr.3 for ; Thu, 18 Aug 2022 15:33:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:from:to:cc; bh=YHQ4Wh5SK0V1LEg6WvbUjjafnUpUy0D2IL3Ade8VZXw=; b=Xa18u0tB7HMzsnmKGxkVoZCzL7kLgnVNbrEM/pnut+g3QuGlZU8T82rRYMT+uH7JX8 mJ2vZoVMfZ7DeQ3N/hRq0QVoE0dHnDCC6jHkB69qMIcAnfLOTXLgyZGlTOdJ4eKUvXXw 4flHnx5l6ko15DdAn6q2TkKoxgnP4dUxXLL/EG6Sv5XUar7vSGs83fHEjEds6EMZiGtz OUBPUoY96/cACPNVbxTxEcH679zbytL6ggf+FUTfKgSAuhsuxedQglqb7+rqBqR9FhJ4 LY0s3HpL/nWX/J45KMRDwAi5O0M0gueWwTXP3KDbK6EUtSzFPD5Sdz9+niAgDzYC3gNx 7x8Q== 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:sender:x-gm-message-state:from:to:cc; bh=YHQ4Wh5SK0V1LEg6WvbUjjafnUpUy0D2IL3Ade8VZXw=; b=4bT+kpMmHfRVRibpralgMXIJUiAZfBulh54X8kiPnBVtmTziS87ILE+P6Q6pB6bGnf 7AByPMA7N6JmSj0n0E6gBB3ZA3uTh8dqMB3MXErTNC3Ty40mglo5NmH+XU7/9WXUn1D1 39ucQycNQb0wRuI0ERAeNYJYxQIi2ddVoJ1fApXkQqC3ZjtOZ9fGbe9cTJnNPEcX52fv LJmJpj828wfphRp9MiQpZPRg0FyM6ZVU7cRnT19eQWG2TKhua5BAgS/EqmV8AVg4Lvbj wWUWFch8U/2pSOrL9NQ3A3GtHFyu0WIBysRbc7uT8N15O0aa0AyW831r89m+gEnqh44N 7+Jw== X-Gm-Message-State: ACgBeo3pKZwymolu5H/y3r8U9DsXSryuuf01xl2aYD9SQUjTlI8nKc2I UOK34GMU4SeItsOSW8z1UlQ= X-Google-Smtp-Source: AA6agR6Xhtkg1508+cxIa3H0yo59iUpgPdxMF1/w3fj7YurA36mIAWVBDXjz/rRfFCZPgfR9CMv5Pw== X-Received: by 2002:a17:903:2310:b0:16e:e0c0:463d with SMTP id d16-20020a170903231000b0016ee0c0463dmr4345769plh.18.1660861984065; Thu, 18 Aug 2022 15:33:04 -0700 (PDT) Received: from localhost ([2620:10d:c090:400::5:3b7]) by smtp.gmail.com with ESMTPSA id x7-20020aa79a47000000b0052d3a442760sm2094200pfj.161.2022.08.18.15.33.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 18 Aug 2022 15:33:03 -0700 (PDT) Date: Thu, 18 Aug 2022 12:33:02 -1000 From: Tejun Heo To: Yafang Shao Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org, kafai@fb.com, songliubraving@fb.com, yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com, haoluo@google.com, jolsa@kernel.org, hannes@cmpxchg.org, mhocko@kernel.org, roman.gushchin@linux.dev, shakeelb@google.com, songmuchun@bytedance.com, akpm@linux-foundation.org, lizefan.x@bytedance.com, cgroups@vger.kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH bpf-next v2 00/12] bpf: Introduce selectable memcg for bpf map Message-ID: References: <20220818143118.17733-1-laoar.shao@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1660862009; h=from:from:sender: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=YHQ4Wh5SK0V1LEg6WvbUjjafnUpUy0D2IL3Ade8VZXw=; b=EUW4Mlt7b90NVHNf7l8aiZvjCEmvgZ7JJxtJ3o00mOJA/Q699oJ4BgprsQ5YzvX9O6/Cxo /CvU+E4rML4NxndCJ6Lr/viKgp75xQQ8Ssszr0oEJWrd8T4Fdzc4+Z2IQzYxvlzuN/yEfL +pX2r/2/FLhRsysBtc5qWU37E5WAj4U= ARC-Authentication-Results: i=1; imf02.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=Xa18u0tB; spf=pass (imf02.hostedemail.com: domain of htejun@gmail.com designates 209.85.216.45 as permitted sender) smtp.mailfrom=htejun@gmail.com; dmarc=fail reason="SPF not aligned (relaxed), DKIM not aligned (relaxed)" header.from=kernel.org (policy=none) ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1660862009; a=rsa-sha256; cv=none; b=t6NUEr/aCDz44gjaBoF1B8GRY2MMpHvsowm+ouuU43YPnZ9n7I1tIJhN9KlJHLIyJt8QQb YIrp2UThXi1QVKdsM+JwE8RUVVgE/NJMmIVUaT5Owht/YfX5xJJvF9LgHXqoXTQnFUTEuJ /+nyke5uaNQiFcVhZuH9tkq808PCflI= Authentication-Results: imf02.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=Xa18u0tB; spf=pass (imf02.hostedemail.com: domain of htejun@gmail.com designates 209.85.216.45 as permitted sender) smtp.mailfrom=htejun@gmail.com; dmarc=fail reason="SPF not aligned (relaxed), DKIM not aligned (relaxed)" header.from=kernel.org (policy=none) X-Rspam-User: X-Rspamd-Queue-Id: DB1828077B X-Rspamd-Server: rspam02 X-Stat-Signature: ooayqy636qi4cnqnq4ygmbdw6ttgpwwy X-HE-Tag: 1660862007-743564 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 18, 2022 at 12:20:33PM -1000, Tejun Heo wrote: > We have the exact same problem for any resources which span multiple > instances of a service including page cache, tmpfs instances and any other > thing which can persist longer than procss life time. My current opinion is To expand a bit more on this point, once we start including page cache and tmpfs, we now get entangled with memory reclaim which then brings in IO and not-yet-but-eventually CPU usage. Once you start splitting the tree like you're suggesting here, all those will break down and now we have to worry about how to split resource accounting and control for the same entities across two split branches of the tree, which doesn't really make any sense. So, we *really* don't wanna paint ourselves into that kind of a corner. This is a dead-end. Please ditch it. Thanks. -- tejun