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 B8D61C77B78 for ; Wed, 3 May 2023 18:24:09 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 4A7086B0072; Wed, 3 May 2023 14:24:09 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 42FD36B0075; Wed, 3 May 2023 14:24:09 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 2F8346B0083; Wed, 3 May 2023 14:24:09 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from mail-pf1-f179.google.com (mail-pf1-f179.google.com [209.85.210.179]) by kanga.kvack.org (Postfix) with ESMTP id 080BB6B0072 for ; Wed, 3 May 2023 14:24:09 -0400 (EDT) Received: by mail-pf1-f179.google.com with SMTP id d2e1a72fcca58-64359d9c531so487091b3a.3 for ; Wed, 03 May 2023 11:24:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683138248; x=1685730248; 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=HAaHXuopg20H7kDrY4ngFywwBOIWWtTHOJdh9Kk4ti8=; b=aB33hUnZnfHPZlWWtIoWkOnjjHisPYabb6S2uWTBQ8h3onE+k8lH1fwWNrmP3+C2Ae V9xYfHUAfa1MQR5bGsnZZI/T3EfAtEbMB7LJgZA6S5DUFfa3NoHlKU045MUvM3dSPcwJ O9knvzOZHAicKc7Q1U9prQ5QYBA7iuXytpIxNnq+/0XAMdmK6s/cx66iKx/7bF6fFMVt 9qvyKftWjNhL52s2yKIZb6lNZsILUvRPIJqsyqINqcoQfODMA3flr2J6lxf4LYnNwpJG HZgaEjG650bHbl05TVNvOqMZG18RkP9d2mBdzyVqPL8pMYePQurNMT2j8/2P3LbRKc10 RP1Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683138248; x=1685730248; 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=HAaHXuopg20H7kDrY4ngFywwBOIWWtTHOJdh9Kk4ti8=; b=RId+LxzMPzgLtscbzODoIBNWVG+ZlGN979bLhr1MlfgbLAUbjKqr41ohIYRDI6QeP4 DRFf6aSKNobUmdsG6Sr1oqeIZOLSfNM0W/1/0Vfv/n/Qxocq9fPOuQMDdvT0ey8xqaaH j1ROiFxmu6QlvRiMQNEeVWpAAqz35CGhauqIJBRlKw9o9av8cOIJnD0v5CKzVG8QJP0f g/YoyOn3XgUYVNZiqdJljntSR0yrIcCutiwVPJP++rKqhOjviOk00R2lTutRajO5YRVK ij80v4wIqML9tVpOhbnShFbBVEob3ILok6uE7maazPXQwxe7O2biz7nDRBbaejamunLy diUQ== X-Gm-Message-State: AC+VfDwwMiXsPoTaLJRmuqidA4pG/8UsjsPgaOJ1cOxjYQBZUm1RAZtd ASRO977PqB9Kw0OYbAwh+rE= X-Google-Smtp-Source: ACHHUZ6SJEEQ8QvbsKtdJRVXR1zPnkUl+hGGIJ5sn55EaO+j6xudf8VpDqWbOhAMlICayQOL4hheYg== X-Received: by 2002:a05:6a20:1616:b0:f3:b764:5de3 with SMTP id l22-20020a056a20161600b000f3b7645de3mr27371733pzj.48.1683138248162; Wed, 03 May 2023 11:24:08 -0700 (PDT) Received: from localhost ([2620:10d:c090:400::5:6454]) by smtp.gmail.com with ESMTPSA id c17-20020a056a000ad100b005ae02dc5b94sm23989633pfl.219.2023.05.03.11.24.06 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 03 May 2023 11:24:07 -0700 (PDT) Date: Wed, 3 May 2023 08:24:05 -1000 From: Tejun Heo To: Kent Overstreet Cc: Michal Hocko , Suren Baghdasaryan , akpm@linux-foundation.org, vbabka@suse.cz, hannes@cmpxchg.org, 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 Subject: Re: [PATCH 00/40] Memory allocation profiling Message-ID: References: <20230501165450.15352-1-surenb@google.com> 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:51:23PM -0400, Kent Overstreet wrote: > Do you have example output? Not right now. It's from many months ago. It's just a script I could find easily. > TBH I'm skeptical that it's even possible to do full memory allocation > profiling with tracing/bpf, due to recursive memory allocations and > needing an index of outstanding allcations. There are some issues e.g. w/ lossy updates which should be fixed from BPF side but we do run BPF on every single packet and IO on most of our machines, so basing this argument on whether tracking all memory allocations from BPF is possible is probably not a winning strategy for this proposal. Thanks. -- tejun