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 EF1B5C48260 for ; Tue, 13 Feb 2024 22:09:24 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 66B4B8D0013; Tue, 13 Feb 2024 17:09:24 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 5F4518D0001; Tue, 13 Feb 2024 17:09:24 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 46E0D8D0013; Tue, 13 Feb 2024 17:09:24 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0016.hostedemail.com [216.40.44.16]) by kanga.kvack.org (Postfix) with ESMTP id 346E78D0001 for ; Tue, 13 Feb 2024 17:09:24 -0500 (EST) Received: from smtpin06.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id 0179E80C3B for ; Tue, 13 Feb 2024 22:09:23 +0000 (UTC) X-FDA: 81788172648.06.6C04EB7 Received: from out-181.mta0.migadu.com (out-181.mta0.migadu.com [91.218.175.181]) by imf07.hostedemail.com (Postfix) with ESMTP id 3420D40019 for ; Tue, 13 Feb 2024 22:09:21 +0000 (UTC) Authentication-Results: imf07.hostedemail.com; dkim=pass header.d=linux.dev header.s=key1 header.b=wiJHD1ro; spf=pass (imf07.hostedemail.com: domain of kent.overstreet@linux.dev designates 91.218.175.181 as permitted sender) smtp.mailfrom=kent.overstreet@linux.dev; dmarc=pass (policy=none) header.from=linux.dev ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1707862162; 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:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=K19bAPZc3Kc3I3XpLB02dh4st8ojApfa6FF0rrEkdlU=; b=RCYSokx6SKLsIdVg4U+TBCFfCzOatKdhVxl071ZvrRMTS6o1qERSkse/TsPA5kaa5WR/0N 7E1mge8NwkxOwzzYVDR4md5N7zexn9BBDeXro1uIutZVWRiEVxtUZe8Dbr4WmVuKoPw3n2 jPBnRPGZ1Yd7iMAzEgMNyEQefiaC1kg= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1707862162; a=rsa-sha256; cv=none; b=pXJzpM8ghWvgJl4Lubx+Zni6nKJbZoeNtSsOYmp+Z7QlGB2E1aj7NliKZkIVAaIMQpMWBj VzF4qdJy005+ttQgAWjZF+62loWTyb44NUfbcQ9QZUDpzSoI8xb99mgZyApH0VwSZBkQJL DytOkU5MHHBUnULGKZCr2yLjXu0nfpg= ARC-Authentication-Results: i=1; imf07.hostedemail.com; dkim=pass header.d=linux.dev header.s=key1 header.b=wiJHD1ro; spf=pass (imf07.hostedemail.com: domain of kent.overstreet@linux.dev designates 91.218.175.181 as permitted sender) smtp.mailfrom=kent.overstreet@linux.dev; dmarc=pass (policy=none) header.from=linux.dev Date: Tue, 13 Feb 2024 17:09:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1707862160; h=from:from: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:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=K19bAPZc3Kc3I3XpLB02dh4st8ojApfa6FF0rrEkdlU=; b=wiJHD1rocU4W8es0ltTxc6zAKxsWq50Cz4wsYEYyTUt+NDk4yTr58JN+k2ZAwaGAMttrjn Ck50Qdg/1aaDREh6YRmyahMrRfD0jYD6p78aHLEPD5//ML214VVyZeX2kIoz692QSHm6HT 8WN0b9HNN/rXmUQrlAmcLAijp1Fq9O8= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Kent Overstreet To: David Hildenbrand Cc: Suren Baghdasaryan , Michal Hocko , 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, 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, axboe@kernel.dk, mcgrof@kernel.org, masahiroy@kernel.org, nathan@kernel.org, dennis@kernel.org, tj@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, vvvvvv@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 v3 00/35] Memory allocation profiling Message-ID: <2hphuyx2dnqsj3hnzyifp5yqn2hpgfjuhfu635dzgofr5mst27@4a5dixtcuxyi> References: <20240212213922.783301-1-surenb@google.com> <9e14adec-2842-458d-8a58-af6a2d18d823@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <9e14adec-2842-458d-8a58-af6a2d18d823@redhat.com> X-Migadu-Flow: FLOW_OUT X-Rspamd-Queue-Id: 3420D40019 X-Rspam-User: X-Rspamd-Server: rspam11 X-Stat-Signature: ojboak5ftgdnnix8mcz8zspwr1mfisss X-HE-Tag: 1707862161-663659 X-HE-Meta: U2FsdGVkX18RxQg5CTaApYR0o5WNTgM2m8yO/FMvqhNC4HWtZ9DIsJMKg5atTN982ZQXnfNjiV3Ec7c/jbSYezLDKZL1EnbfPUVyd3EtrpF+eihXqlZqj5ukSdY6fQa1TVpwNh6Kqu6gyPch0xoak7mWPSvCj4XDKAjoRa/rYO2zfiQxhzYmLcrn3jgE6XwRpBRS1qH1URe4V3ZsxHX/qebH+GWSv/VGnFOuMbY81MUHXqlhV7eBmTV9tVv/QcoYtvwigZvTev3MppQkTAHTSMoMGjWpp/okL9R9gpAkk8vnvzWjKENAL15YCUfVsI+j6eHRm/sHMi0ZJFmUzdQYgtgpCQ6u5Bg5Xj6OqGUzDNMKR9Q6Yxd9Ba1d1H8hMOzX5dmw5/eTavF1gDll8k1WvQKIVLrFXaf8nk4i7qSyg1ej6hUfkHFtrD7e+CTNyQK3TOu5L1FgVxA/ygyaZO+D9U9humbc6paAd2W6QCAtJgmpFcdktdr/JiOoYdozCZ46FgxSPGwkO5+w1xz58ULW6sScGX6Meq9tnvblv2IEoQob0YDqWqMfjEwEEJLOn/ovkxttJvHoz9YaJgrnSYZxj9Dss0nal5E5j3ltdqNcFNOg6KIv/jcjI1/ddtmYcsUvl7U89jOzH38TcpwgPQ60sNhWJRBuX/OMBYCpQ8q1vm7HDdwmGcI47vg5tk3steOrN1Wb+8J+EN8dHuyJ3TjidE7MrpcgItCh5NGmVepd38ZtMNuqXToqccnTA7jjIQDICaiqWjADc/WKH9Uz2LOW94YPqFPuF4WE2lOoGxt/rqqUTMe4u/3wZFXydvAo1htv65gz2z4CpXtN+Q+koQAXgfaXvOiOIqNmNvd8Gur8z1E+dHTQgYMg0W72rDrkiADXOi95S/FMXTx/RyRpJGNzSD3JuVfL/QxaoFakErvqPavO6TgbsGeiwjOPeulUGGgqFjQ5jcqigOjbi8oMSdI ZAv6Guvm DKYVXBOrJ0v6/QqPFapirtO2hCu6x1dsKVXVKvqHQ1xP+94n7dvxRNfAw7BUUqZ1G8qpldIlEFtFupSxJEN33sP0Q0lzF6muiI4/LGqtVaUJIrIDAnX2qdzPEDlnYmGDpoAWRHcWJidA+yzAJlyQMc+i/lKJ9egh5+3JbsFVEKdD+CuRG+yuNI95ju/gEW3s/rolSefVc0mYBoV+6mOljv+RAkrmFytGlF7DlVEaJnp65rFtRDDgQlgiWJQ== 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: List-Subscribe: List-Unsubscribe: On Tue, Feb 13, 2024 at 11:04:58PM +0100, David Hildenbrand wrote: > On 13.02.24 22:58, Suren Baghdasaryan wrote: > > On Tue, Feb 13, 2024 at 4:24 AM Michal Hocko wrote: > > > > > > On Mon 12-02-24 13:38:46, Suren Baghdasaryan wrote: > > > [...] > > > > We're aiming to get this in the next merge window, for 6.9. The feedback > > > > we've gotten has been that even out of tree this patchset has already > > > > been useful, and there's a significant amount of other work gated on the > > > > code tagging functionality included in this patchset [2]. > > > > > > I suspect it will not come as a surprise that I really dislike the > > > implementation proposed here. I will not repeat my arguments, I have > > > done so on several occasions already. > > > > > > Anyway, I didn't go as far as to nak it even though I _strongly_ believe > > > this debugging feature will add a maintenance overhead for a very long > > > time. I can live with all the downsides of the proposed implementation > > > _as long as_ there is a wider agreement from the MM community as this is > > > where the maintenance cost will be payed. So far I have not seen (m)any > > > acks by MM developers so aiming into the next merge window is more than > > > little rushed. > > > > We tried other previously proposed approaches and all have their > > downsides without making maintenance much easier. Your position is > > understandable and I think it's fair. Let's see if others see more > > benefit than cost here. > > Would it make sense to discuss that at LSF/MM once again, especially > covering why proposed alternatives did not work out? LSF/MM is not "too far" > away (May). > > I recall that the last LSF/MM session on this topic was a bit unfortunate > (IMHO not as productive as it could have been). Maybe we can finally reach a > consensus on this. I'd rather not delay for more bikeshedding. Before agreeing to LSF I'd need to see a serious proposl - what we had at the last LSF was people jumping in with half baked alternative proposals that very much hadn't been thought through, and I see no need to repeat that. Like I mentioned, there's other work gated on this patchset; if people want to hold this up for more discussion they better be putting forth something to discuss.