linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Suren Baghdasaryan <surenb@google.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	 Kent Overstreet <kent.overstreet@linux.dev>
Subject: [LSF/MM/BPF TOPIC] Memory profiling using code tagging
Date: Wed, 22 Feb 2023 11:31:35 -0800	[thread overview]
Message-ID: <CAJuCfpHJX8zeQY6t5rrKps6GxbadRZBE+Pzk21wHfqZC8PFVCA@mail.gmail.com> (raw)

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.

Kent Overstreet, Michal Hocko, Johannes Weiner, Matthew Wilcox, Andrew
Morton, David Hildenbrand, Vlastimil Babka, Roman Gushchin would be
good participants.

[1] https://lwn.net/Articles/906660/
[2] https://lore.kernel.org/all/20220830214919.53220-1-surenb@google.com/


             reply	other threads:[~2023-02-22 19:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 19:31 Suren Baghdasaryan [this message]
2023-03-28 16:28 ` Vlastimil Babka
2023-03-28 16:55   ` Kent Overstreet
2023-05-10 16:28   ` Kent Overstreet
2024-01-21 23:39     ` Pasha Tatashin
2024-01-21 23:56       ` Kent Overstreet
2024-01-22  1:18       ` Matthew Wilcox
2024-01-22  3:29         ` Suren Baghdasaryan
2023-05-10 16:26 ` Suren Baghdasaryan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJuCfpHJX8zeQY6t5rrKps6GxbadRZBE+Pzk21wHfqZC8PFVCA@mail.gmail.com \
    --to=surenb@google.com \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox