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 78DA5C433EF for ; Tue, 12 Jul 2022 16:32:38 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id EBAAE9400A7; Tue, 12 Jul 2022 12:32:37 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id E6988940063; Tue, 12 Jul 2022 12:32:37 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id D0BF69400A7; Tue, 12 Jul 2022 12:32:37 -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 BEAD0940063 for ; Tue, 12 Jul 2022 12:32:37 -0400 (EDT) Received: from smtpin01.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay11.hostedemail.com (Postfix) with ESMTP id 9639280E10 for ; Tue, 12 Jul 2022 16:32:37 +0000 (UTC) X-FDA: 79678991154.01.AF30910 Received: from mail-pg1-f172.google.com (mail-pg1-f172.google.com [209.85.215.172]) by imf17.hostedemail.com (Postfix) with ESMTP id 315B740069 for ; Tue, 12 Jul 2022 16:32:37 +0000 (UTC) Received: by mail-pg1-f172.google.com with SMTP id q82so8049035pgq.6 for ; Tue, 12 Jul 2022 09:32:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=36hChXhZD7e1BU/dCd5AJq0lPf1x1NPmuTN2tiYyqjA=; b=n7ZqeU7FP4t8OZIU4MjHTqGUXqcx3+vlKlvrKCLQLjt+yzW680ldGOeekZTql0alb+ 9VkZBDwTTM84TYnklqeE1egnG0iijOn5hTss7iT8dmY1asJQ78EvwC/o8bVcwQ/NESXb fp4M+orUI5M8SBluiWSlzk2OLHcEg/QdfnCRz+bQdguB6QB4ZftrjsDo5+I5TlqLanB8 1+CTfYNBq/EBIn2vXVI0hPQJfR4tFQZJMEbAvMGSJlAQrtRutLh1POlBif0UOGpcEuTs 7kTliSXb4LDnob31gooijEbqSlAagHDiI7+E7nOJgQuBrgb7C5y/NKmxPU8awEe0agWD uTfQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to; bh=36hChXhZD7e1BU/dCd5AJq0lPf1x1NPmuTN2tiYyqjA=; b=FkqysjhaK1dwFFUze/hB0HwCwHYdyQfctYlTcUnkeXnHmBDXgKh/YZAPJzWbzB6WBX mfHk3StZ7H2CEV1uuMXakNZNAMh9twNEPtyKm/Avj48pQ37gn9asRF1Yyu5zZnuNRQo2 xz9F6eFRsxRc6gaH3A/BGukykyYdFr1kro2VCtCXwLIbVUwJXiDh9Zcjue3DsyE2mOkc cjHHtK/7gd4o/Yy7shoTAeWg81kElYOJoCnyGHiQ86Cvf3qrNpZvTr4cGKn0hgdJLho0 L97TWhSgoegrMJt01h79/W5l6JrnP25XYKUKZMzpaoczby+06AaYx72q/w8EklAyVFcU CIuQ== X-Gm-Message-State: AJIora9H+mndv9YTi5cdElVVvgon/14p7cMIiGu+H/jbXcIiPdJOdn21 kPhQyIwxxR2tRI7DL6BMft8= X-Google-Smtp-Source: AGRyM1uhOPbLyK+2uJv53/vsPqdhlVh6Yck3gq7c1UoyjUwufYFEuAvg5FaopQhIYlah2Rti2loT1g== X-Received: by 2002:a05:6a00:9a0:b0:52a:e646:d90c with SMTP id u32-20020a056a0009a000b0052ae646d90cmr4586657pfg.86.1657643555999; Tue, 12 Jul 2022 09:32:35 -0700 (PDT) Received: from localhost (2603-800c-1a02-1bae-a7fa-157f-969a-4cde.res6.spectrum.com. [2603:800c:1a02:1bae:a7fa:157f:969a:4cde]) by smtp.gmail.com with ESMTPSA id 70-20020a621549000000b0050dc76281d3sm7165937pfv.173.2022.07.12.09.32.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 12 Jul 2022 09:32:35 -0700 (PDT) Date: Tue, 12 Jul 2022 06:32:33 -1000 From: Tejun Heo To: Shakeel Butt Cc: Michal Hocko , Yosry Ahmed , Muchun Song , Johannes Weiner , Yafang Shao , Alexei Starovoitov , Matthew Wilcox , Christoph Hellwig , "David S. Miller" , Daniel Borkmann , Andrii Nakryiko , Martin KaFai Lau , bpf , Kernel Team , linux-mm , Christoph Lameter , Pekka Enberg , David Rientjes , Joonsoo Kim , Andrew Morton , Vlastimil Babka Subject: Re: [PATCH bpf-next 0/5] bpf: BPF specific memory allocator. Message-ID: References: <20220708174858.6gl2ag3asmoimpoe@macbook-pro-3.dhcp.thefacebook.com> <20220708215536.pqclxdqvtrfll2y4@google.com> <20220710073213.bkkdweiqrlnr35sv@google.com> <20220712043914.pxmbm7vockuvpmmh@macbook-pro-3.dhcp.thefacebook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1657643557; a=rsa-sha256; cv=none; b=ioei1Fxh+9G54CKmShp/d3WJoXsAI44BTcvtk+L6TvCeas5XzDCqCpuLETAlXMIhcxv6f0 naCvS/X8mPiqKeAxQTQP9MUkTpdOxcKChIPjuxpyWzJIsCgxBIA2qA0iFrLLpcKas3TGw2 CrvCw0hMnk5XUVW8/djl5Pfgsu7io1M= ARC-Authentication-Results: i=1; imf17.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=n7ZqeU7F; spf=pass (imf17.hostedemail.com: domain of htejun@gmail.com designates 209.85.215.172 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-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1657643557; 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=36hChXhZD7e1BU/dCd5AJq0lPf1x1NPmuTN2tiYyqjA=; b=CCgMu9qi8FMzAPF78GbbGxqxefbOq08ouJbfYsFUpzsUqWQGkgrged9RLFTwInbHlG+koZ KzR68kvVKoBYIJj7dbwt7L3qh9VeIcEM1FfhPcJtCJxT+ZJstojBxwGW5AH0hm5O+b9btM Z8Cxl3bk4aBfQRL3zyNI/7FE16MOH24= X-Rspamd-Server: rspam06 X-Rspamd-Queue-Id: 315B740069 X-Rspam-User: Authentication-Results: imf17.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=n7ZqeU7F; spf=pass (imf17.hostedemail.com: domain of htejun@gmail.com designates 209.85.215.172 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-Stat-Signature: 7tnsxb18tijfsb3yc5h8u9c5y119qz6r X-HE-Tag: 1657643557-50431 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: Hello, On Tue, Jul 12, 2022 at 08:25:24AM -0700, Shakeel Butt wrote: > Another very obvious example is the filesystem shared between multiple > jobs. We had a similar discussion [1] on LRU reparenting patch series. Hmm... if I'm understanding correctly, what's discussed in [1] can be solved with proper reparenting and nesting, right? > For this use-case internally we have a memcg= mount option where the > given memcg is the common ancestor (think of pod in k8s environment) > of the jobs who are sharing the filesystem. Can you elaborate a bit more on this? We've never really supported correctly accounting pages shared across cgroups because it can be very complicating and the use cases aren't that wide-spread. What's being shared? How big is the shared portion in relation to total memory usage? What's the cgroup topology like? Thanks. -- tejun