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 ACA42C6FD18 for ; Tue, 28 Mar 2023 16:56:00 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 04ECE6B0071; Tue, 28 Mar 2023 12:56:00 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id F41386B0072; Tue, 28 Mar 2023 12:55:59 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id E30596B0074; Tue, 28 Mar 2023 12:55:59 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0015.hostedemail.com [216.40.44.15]) by kanga.kvack.org (Postfix) with ESMTP id D4B736B0071 for ; Tue, 28 Mar 2023 12:55:59 -0400 (EDT) Received: from smtpin16.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay08.hostedemail.com (Postfix) with ESMTP id 97449140A20 for ; Tue, 28 Mar 2023 16:55:59 +0000 (UTC) X-FDA: 80618909238.16.9E71415 Received: from out-37.mta1.migadu.com (out-37.mta1.migadu.com [95.215.58.37]) by imf01.hostedemail.com (Postfix) with ESMTP id B2D7F40012 for ; Tue, 28 Mar 2023 16:55:56 +0000 (UTC) Authentication-Results: imf01.hostedemail.com; dkim=pass header.d=linux.dev header.s=key1 header.b=VkJqDZG+; dmarc=pass (policy=none) header.from=linux.dev; spf=pass (imf01.hostedemail.com: domain of kent.overstreet@linux.dev designates 95.215.58.37 as permitted sender) smtp.mailfrom=kent.overstreet@linux.dev ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1680022557; 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: in-reply-to:in-reply-to:references:references:dkim-signature; bh=hxBJnNBm/cNkHCZcwSILQF6wnG9ilV9aQydMGT1rWvc=; b=lNrJGpQiIFkQ49oDEWsueGBun/zK/YunjnmLdmyAF9S7gmSnjNx08/EF7V3m02bUqs0t0w KFZ7+ezGr5cIndIQ2RQ1tfeFo3Jvl7M1c3hukiM1nJQFgllZkStg6LvYT+le5FctQHhbSw 68etO0JGlqDGeRJvr9sBcdUpT8zpw+0= ARC-Authentication-Results: i=1; imf01.hostedemail.com; dkim=pass header.d=linux.dev header.s=key1 header.b=VkJqDZG+; dmarc=pass (policy=none) header.from=linux.dev; spf=pass (imf01.hostedemail.com: domain of kent.overstreet@linux.dev designates 95.215.58.37 as permitted sender) smtp.mailfrom=kent.overstreet@linux.dev ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1680022557; a=rsa-sha256; cv=none; b=Y4YWXTyAsCDlcbUjg52gJD1CNRSi2ScxmkxSS+3fiO3viV9KIBQAquH549Gpwn5v+e0QBT 5/Tl3J94IAlv8f9fZlqI1I0xrggwRgq1tqr0jl4v4fUC9C++FyxYc321MhvhXNFWbqy9O1 lTBbna/lbMTIIzXxQmLinXXPxlJRGpw= Date: Tue, 28 Mar 2023 12:55:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1680022554; 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: in-reply-to:in-reply-to:references:references; bh=hxBJnNBm/cNkHCZcwSILQF6wnG9ilV9aQydMGT1rWvc=; b=VkJqDZG+29d//8LLQh/wx5LDGNqIe/T2Z+MMrUsnWdQTtA3opKIdt/us+IYc7a1GHMTVQG cTx67DsHRe2UY5fIl8hBB9LNV0MF5SoMWxOhsPuEjr35k2K+zviAiWLCJ25s1q5Yv9gJmQ IlXq1BeUjhk4eys036gB7dm6q8f5GkM= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Kent Overstreet To: Vlastimil Babka Cc: Suren Baghdasaryan , lsf-pc@lists.linux-foundation.org, linux-fsdevel , linux-mm Subject: Re: [LSF/MM/BPF TOPIC] Memory profiling using code tagging Message-ID: References: <115288f8-bd28-f01f-dd91-63015dcc635d@suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <115288f8-bd28-f01f-dd91-63015dcc635d@suse.cz> X-Migadu-Flow: FLOW_OUT X-Rspamd-Queue-Id: B2D7F40012 X-Rspamd-Server: rspam09 X-Rspam-User: X-Stat-Signature: bep96w5cjpojn7bkor3ab4aoqms7s7ra X-HE-Tag: 1680022556-530810 X-HE-Meta: U2FsdGVkX1/6zNK3RBIQKI/zD8Nwl2bGKvGX4vUqZAHKGktRMaO/7CQ14QUHgTluJ9lMlNAVxKGwRw53ruoWRBm4MVkQvGql0/iC+LkX25ruaCBihzOBOKtSI/sIvrScbmZCXyOacqVO6XePfwbfJY9ayppvulg6YkOQa/5PalspjtESZiBhPQKOxIL4896RrsRk+7at6UjvyP+tAooq4JDhW52GdKtb8/+coywerB8JaBEUKPc9beJw4CLLdjCytERckBqcwaWUWlIK+gDmb1DXHxCJijjCpBts4IggMKIKjLPCUYImhvaAqWIHzCQxAGjDknszgpvdr0B3SU8LnYe39vA+iu0YXXzIfVrjWUp/fA0zSqUxpcHbIzC/dPrl3huj8WpKnYTNc/86WWQnIIn7aMtNqR6mqW9LHhFmmjr/NUFx3ZZ/aWDKsj6bzbd80EADbGo6cEwvNj8mY0B3sx62REnoLR9SUyDLUOHloQS/WBEkulbeyLZCnhHDWjXBe/3rNI3vsDyM7HLzxrjqXZ7ymf6NHp5ZGGOQKqIL/snNXR2EiXlSVkWygtLYtFCOhjkKaI7Yv2skSc0HsCZrG8RuQrBkFZLhddDz7yR1P/DkUs77PTMo0sdHrzanrl1bRWDsrwaY6OiKdYguvfBzjGb/DKekZ7+aOMboeEQaIKbe+Q37rVgWyH5AeGx2cOdqMK/X0XtZIeWxJZUA2e1+N1WtuW0zchGospQ9KMfqlD8nc0aMulPf4IE2EZix+Ti/ERe8a2GtfL50QU+5+JDanDLRimH+7/XjS2C+wDhwHf5bngNjUUkCiwls97kqOAwIzQrZfyOXJWXeacj94B9uL8qQXo++NKQDbS7oUr/g31rihKurW3d81L8c+VIV5FNH1D8wASHLo+9YqVMqLpEqxwGD0Uq4E8Dy5DLerfLtuyPi0VFQrdBIEZYWHZUm3YPJj0KkyqQWEaZqiIAmMdj INl8uxOg JGBCFGTEOEApZMPZSGpqHeh5Woo7sKcEBQpR+ydhoWeAJdEaVPnAHGiAhUr0aUwHQfdDv 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 Tue, Mar 28, 2023 at 06:28:21PM +0200, Vlastimil Babka wrote: > On 2/22/23 20:31, Suren Baghdasaryan wrote: > > We would like to continue the discussion about code tagging use for > > memory allocation profiling. The code tagging framework [1] and its > > applications were posted as an RFC [2] and discussed at LPC 2022. It > > has many applications proposed in the RFC but we would like to focus > > on its application for memory profiling. It can be used as a > > low-overhead solution to track memory leaks, rank memory consumers by > > the amount of memory they use, identify memory allocation hot paths > > and possible other use cases. > > Kent Overstreet and I worked on simplifying the solution, minimizing > > the overhead and implementing features requested during RFC review. > > IIRC one large objection was the use of page_ext, I don't recall if you > found another solution to that? No, page_ext is really the thing that makes the most sense here. It's per-page allocation information, so the only other place it could go is in struct page itself - but that doesn't make any sense with the boot time option we've got now, page_ext works perfectly with that.