linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: David Rientjes <rientjes@google.com>
Cc: SeongJae Park <sj@kernel.org>, Michal Hocko <mhocko@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mel Gorman <mgorman@suse.de>,
	Balbir Singh <bsingharora@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-mm@kvack.org, damon@lists.linux.dev
Subject: Re: Tools for explaining memory mappings/usage/pressure
Date: Sun,  7 Jul 2024 08:44:27 -0700	[thread overview]
Message-ID: <20240707154428.77697-1-sj@kernel.org> (raw)
In-Reply-To: <29c27dab-a590-5df2-c840-279bf9dff090@google.com>

Hi David,

On Sat, 6 Jul 2024 13:55:11 -0700 (PDT) David Rientjes <rientjes@google.com> wrote:

[...]
> Rather than hacky scripts that collect things like vmstat, memory.stat, 
> buddyinfo, etc, at regular intervals, it would be preferable to hand off 
> something more complete.  Idea is an open source tool that can be run in 
> the background to collect metrics for the system, NUMA nodes, and memcg 
> hierarchies, as well as potentially from subsystems in the kernel like 
> delay accounting.  IOW, I want to be able to say "install ${tool} and send 
> over the log file."
> 
> Are thre any open source tools that do a good job of this today that I can 
> latch onto?

DAMON user-space tool, damo[1], provides background recording and reporting of
memory access information including size of memory showing specific access
pattern (e.g., working set size).  Nowadays we're extending the tool to capture
and provide more information for holistic and intuitive system investigations.
Currently basic memory footprints and CPU usage of functions are provided.

The current status of the tool would be far from what you're looking for,
though.  I'm also not sure if current future plan of the tool would perfectly
meet your requirements.  We're open to any contributions to damo, though.

Hopefully others may know better tools for this.  I'm looking forward to a
chance to learn from those.

> If not, sounds like I'll be writing one from scratch.  Let me 
> know if there's interest in this as well.

We're open at not only receiving contributions for damo, but also providing
contributions to other projects (and using it).  So, yes, I'm interested in
this :)

[1] https://github.com/awslabs/damo

Thanks,
SJ

> 
> Thanks!


  reply	other threads:[~2024-07-07 15:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-06 20:55 David Rientjes
2024-07-07 15:44 ` SeongJae Park [this message]
2024-07-08 13:50 ` Dan Schatzberg
2024-07-21 23:05   ` David Rientjes
2024-07-22 22:15     ` Dan Schatzberg
2024-07-22  9:05 ` Vlastimil Babka (SUSE)
2024-07-22 21:57   ` David Rientjes
2024-12-30  8:15 ` Raghavendra K T

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=20240707154428.77697-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bsingharora@gmail.com \
    --cc=damon@lists.linux.dev \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mhocko@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rientjes@google.com \
    /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