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 C70C0C77B7C for ; Wed, 10 May 2023 16:28:57 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 686E76B0072; Wed, 10 May 2023 12:28:57 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 636D56B0074; Wed, 10 May 2023 12:28:57 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 525C46B0075; Wed, 10 May 2023 12:28:57 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id 45C576B0072 for ; Wed, 10 May 2023 12:28:57 -0400 (EDT) Received: from smtpin23.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id F3BFE80156 for ; Wed, 10 May 2023 16:28:56 +0000 (UTC) X-FDA: 80774879472.23.4D4FBFD Received: from out-16.mta1.migadu.com (out-16.mta1.migadu.com [95.215.58.16]) by imf03.hostedemail.com (Postfix) with ESMTP id E59C120019 for ; Wed, 10 May 2023 16:28:53 +0000 (UTC) Authentication-Results: imf03.hostedemail.com; dkim=pass header.d=linux.dev header.s=key1 header.b=ZYe80aIK; spf=pass (imf03.hostedemail.com: domain of kent.overstreet@linux.dev designates 95.215.58.16 as permitted sender) smtp.mailfrom=kent.overstreet@linux.dev; dmarc=pass (policy=none) header.from=linux.dev ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1683736134; a=rsa-sha256; cv=none; b=j0LR3a306kCxVz9+44XWniSOJYI/t86ckk0uXlOZoWjyIVDfvr+ocTCRWmwzG4aFhVhHY3 PkTrbVGgTR/24U80UgypurhY3xP/sIQ7yyCgycjrxYrCyLw5EF02coMOlhU0u+T+Zvrftf 3PagyTdxZhZpk4sE1lENzjHHm5qvyQw= ARC-Authentication-Results: i=1; imf03.hostedemail.com; dkim=pass header.d=linux.dev header.s=key1 header.b=ZYe80aIK; spf=pass (imf03.hostedemail.com: domain of kent.overstreet@linux.dev designates 95.215.58.16 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=1683736134; 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=BYcJ9BZ1mxYTmW6a8/38gfY091GqMcL8DJ8glX2OZQM=; b=Ybr4deS3W30oRntdPQ0m+et+PqXATVESkvBC+pcKSpyoZksbamITD7BNbE9jSw/0Hg33Q3 dvcqhFk++B1DBGL5YLXRvjJQXjq+HmrBqauMZtLet3I8xNDLCa3rPNf9clb1Rpwc4JHzjR 9UPx9yyJHgJLlgXOvLXTXO5L0djitqM= Date: Wed, 10 May 2023 12:28:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1683736131; 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=BYcJ9BZ1mxYTmW6a8/38gfY091GqMcL8DJ8glX2OZQM=; b=ZYe80aIKHQFU6hSAnJo2ZOlHsjm4xX3rHplLPiNn21AGUtOPosTr4ICG+ZcNJqHqfFBJ6k AM6pIJZQlYs536/8A80yRxHX1/mhn7F0jQaGfENHZrCoWKR0zVyfPzoD/iKV6aRwBbccwM Gma38xXl1JcPxsrMlN929YPlxFobjmQ= 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-Rspam-User: X-Stat-Signature: jdjcrjp1jn43xo5sfty3xxqfad188yra X-Rspamd-Server: rspam08 X-Rspamd-Queue-Id: E59C120019 X-HE-Tag: 1683736133-769068 X-HE-Meta: U2FsdGVkX19abiP6DXMPI8kyx0v3vAmI7TFcEAi157c7XlfNlVSLvXCRs8N8yXVv+xIQfyYe+Nv/8R+b5PKzVxxOiv0dAy2P+jwBwKHf3NWZ4sYHFy1STrb4fmir1qMC2VKpGhNh4L3va8h0xrIm0VhFH9D8Onk1770SoT3LGmY+DH9XK7KvrfEU5h72yoy7n6SJlEZrbnul3g6kBZatlMHigs0bkh5RT0atR3iaVmAbn43I28RJBcnge0b+sOdcKJcDxP6J6Q4QJZ/Kwh548Px7CC/OcWeKkL5V+FPISY9zDQWaT4RIw0y7qa7olfTSJm57O3k6itByMqbJmZPIHfu+FzDi80ENJSh5kjpj3WwSXrNGHEh0lW8Z2xoKQ7S+gicWReKSexeevfb+SNPsKdaGyvc44v/qQyNOMtmokdRyPwSwlR0KotyHVN7vwXRVUoCP4SeIaqt+QolPapn2t0ZyUh7WyR1KT2wB1IHgqe//eRap/RRUc1FlusSlPhfgDJjvXfx/UjmjsrGyhriE/YCsaBWAWYTd6G6qOcFAU9y1G6c4VTxxk8zcRET5vSkcm/b2vgDpJ/L7fRsR1d0Ze+4KU5Jm3a1I9yz9eyKStp0wVIf/zNahhrF/AyrFxLd3YZwSVN2kkzSNHL5wDrYGHnzTTGzpSrzh6r8Q8R4wurUSkJ8Ylkb6vzheOyfIcppgjfVVlAL6d9ONhNrMJ0v4+7NpBoilGUTJo29O0+CYYa7+ikCAdzqIkvH6plaWtoAALApl5cK41snhwilUArDEFsMC73QbKob2YsWYDmm0BIWINTNuvyNV5XR7M1UK3225Dk2j/tRwIUqL8XUxaoanbFLjY1eGinTiDk0EQIjyk8zBdYOY5NDkwk+UooveCpHDSmJcAXwVzktay1An+BYbjNrXbefJiuY394CjLYyFIjsAGfRs3QD8HsGzFbTtQ1dBWeHoqmi3Ta4WbQehYXA wdHESOu9 rL2QUNXMU5ZFpK9pcsbkzrEu09Ux7XAVEVwC043+cHz1L+4o= 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? Hasn't been addressed yet, but we were just talking about moving the codetag pointer from page_ext to page last night for memory overhead reasons. The disadvantage then is that the memory overhead doesn't go down if you disable memory allocation profiling at boot time... But perhaps the performance overhead is low enough now that this is not something we expect to be doing as much? Choices, choices...