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 4B768C77B7F for ; Thu, 4 May 2023 02:16:49 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 74FCE6B0075; Wed, 3 May 2023 22:16:48 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 6D8F36B0078; Wed, 3 May 2023 22:16:48 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 579866B007B; Wed, 3 May 2023 22:16:48 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from mail-pf1-f178.google.com (mail-pf1-f178.google.com [209.85.210.178]) by kanga.kvack.org (Postfix) with ESMTP id 199E86B0075 for ; Wed, 3 May 2023 22:16:48 -0400 (EDT) Received: by mail-pf1-f178.google.com with SMTP id d2e1a72fcca58-63b5465fc13so4178b3a.3 for ; Wed, 03 May 2023 19:16:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683166607; x=1685758607; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:from:to:cc:subject:date:message-id :reply-to; bh=xki9EImbF8EHplkOG7u13eoQc3pPoVT6i0i48IKNO48=; b=AVbZGT9K0r89MqzrSpIR7uMQXdw8u/F4834X6xnRREOGxmDQ4D/A6MjHGUxFG3npis aSiP7azLezP1XiGgrGudWR33IUl22a/61L8gQoe/STrWaRoCtDxodSejGGl7LbFwoSoW y8er0cowxZ+SiTuo8NZyP0h49wpyK2kMLhUVxrO1AuEfSIV5AQV6s/WtZ233X+EY2wzS HnH2l/EQfk2fmkfN3WEcKcwTa+M18CB0b6bZWDe3dFh5+ms0vEqPkw0zF+C7i7OAyOn6 4mDKRPiK7AP3pPjuxFNw9ey2zSAa4AXCrWoax2bREtiC64a4zO5i43E6Ply2PNr5/uI6 ybJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683166607; x=1685758607; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=xki9EImbF8EHplkOG7u13eoQc3pPoVT6i0i48IKNO48=; b=YEHM9yf8CIMhen+GLNa6r9Zxu3RFTO+XEHojRMGiR13uMLDs1KfShzQ0b1NH/MFFpU Sc1hcdrK981uN7zQM5cFbAOxGSyNnN6eplO42HYQCaPGIq/UiXBhenZgdnG5MpqC/SIO L3dect1L9SNCbuORRVfiYzuxFpkXPpuVEadKG6j4O1b+meAbMygERN2YzLeBcba/BKCy h0wDe+FqbA0StTvVer3PEuL2DWBtFBSFbD1KV5ZQPp76yx3oN+ylc+ZB+iDx1sBTuibv Kk6zyhNbNZ7VyTckv+5amrf2n+iIWStXNKXfzm08DyCbHGbmpvMO9YjAzl8UzX1gRl14 7l2A== X-Gm-Message-State: AC+VfDze5JrlX3e6a7RYxaLa3GWyRyU1VGe/sG/Dc4dGDBov/ekT52U/ ogdTpjZU7lSJ7opTLhsBD3Y= X-Google-Smtp-Source: ACHHUZ586dtnZJkOKWi8qtW2XOPFy14umbO1JQg1ZdQXQttGCitXUXieeRChBtu6pNojzrEGrsn1pA== X-Received: by 2002:a17:902:a60e:b0:1a9:2b7f:a594 with SMTP id u14-20020a170902a60e00b001a92b7fa594mr1984126plq.29.1683166606837; Wed, 03 May 2023 19:16:46 -0700 (PDT) Received: from localhost ([2620:10d:c090:400::5:6454]) by smtp.gmail.com with ESMTPSA id jd20-20020a170903261400b001a682a195basm3871260plb.28.2023.05.03.19.16.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 03 May 2023 19:16:46 -0700 (PDT) Date: Wed, 3 May 2023 16:16:44 -1000 From: Tejun Heo To: Suren Baghdasaryan Cc: Kent Overstreet , Johannes Weiner , Michal Hocko , akpm@linux-foundation.org, vbabka@suse.cz, roman.gushchin@linux.dev, mgorman@suse.de, dave@stgolabs.net, willy@infradead.org, liam.howlett@oracle.com, corbet@lwn.net, void@manifault.com, peterz@infradead.org, juri.lelli@redhat.com, ldufour@linux.ibm.com, catalin.marinas@arm.com, will@kernel.org, arnd@arndb.de, tglx@linutronix.de, mingo@redhat.com, dave.hansen@linux.intel.com, x86@kernel.org, peterx@redhat.com, david@redhat.com, axboe@kernel.dk, mcgrof@kernel.org, masahiroy@kernel.org, nathan@kernel.org, dennis@kernel.org, muchun.song@linux.dev, rppt@kernel.org, paulmck@kernel.org, pasha.tatashin@soleen.com, yosryahmed@google.com, yuzhao@google.com, dhowells@redhat.com, hughd@google.com, andreyknvl@gmail.com, keescook@chromium.org, ndesaulniers@google.com, gregkh@linuxfoundation.org, ebiggers@google.com, ytcoode@gmail.com, vincent.guittot@linaro.org, dietmar.eggemann@arm.com, rostedt@goodmis.org, bsegall@google.com, bristot@redhat.com, vschneid@redhat.com, cl@linux.com, penberg@kernel.org, iamjoonsoo.kim@lge.com, 42.hyeyoo@gmail.com, glider@google.com, elver@google.com, dvyukov@google.com, shakeelb@google.com, songmuchun@bytedance.com, jbaron@akamai.com, rientjes@google.com, minchan@google.com, kaleshsingh@google.com, kernel-team@android.com, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, iommu@lists.linux.dev, linux-arch@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-modules@vger.kernel.org, kasan-dev@googlegroups.com, cgroups@vger.kernel.org, Alexei Starovoitov , Andrii Nakryiko Subject: Re: [PATCH 00/40] Memory allocation profiling Message-ID: References: <20230503180726.GA196054@cmpxchg.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Wed, May 03, 2023 at 01:08:40PM -0700, Suren Baghdasaryan wrote: > > Yeah, I was wondering whether it'd be useful to have that configurable so > > that it'd be possible for a user to say "I'm okay with the cost, please > > track more context per allocation". > > I assume by "more context per allocation" you mean for a specific > allocation, not for all allocations. > So, in a sense you are asking if the context capture feature can be > dropped from this series and implemented using some other means. Is > that right? Oh, no, what I meant was whether it'd make sense to allow enable richer tracking (e.g. record deeper into callstack) for all allocations. For targeted tracking, it seems that the kernel already has everything needed. But this is more of an idle thought and the immediate caller tracking is already a big improvement in terms of visibility, so no need to be hung up on this part of discussion at all. Thanks. -- tejun