All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	James Clark <james.clark@linaro.org>,
	Thomas Falcon <thomas.falcon@intel.com>,
	Thomas Richter <tmricht@linux.ibm.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] Add procfs based memory and network tool events
Date: Wed, 7 Jan 2026 00:08:04 -0800	[thread overview]
Message-ID: <aV4UZCCc2QOhdeSE@google.com> (raw)
In-Reply-To: <20260104011738.475680-1-irogers@google.com>

Hi Ian,

On Sat, Jan 03, 2026 at 05:17:36PM -0800, Ian Rogers wrote:
> Add events for memory use and network activity based on data readily
> available in /prod/pid/statm, /proc/pid/smaps_rollup and
> /proc/pid/net/dev. For example the network usage of chrome processes
> on a system may be gathered with:
> ```
> $ perf stat -e net_rx_bytes,net_rx_compressed,net_rx_drop,net_rx_errors,net_rx_fifo,net_rx_frame,net_rx_multicast,net_rx_packets,net_tx_bytes,net_tx_carrier,net_tx_colls,net_tx_compressed,net_tx_drop,net_tx_errors,net_tx_fifo,net_tx_packets -p $(pidof -d, chrome) -I 1000
>      1.001023475                  0      net_rx_bytes
>      1.001023475                  0      net_rx_compressed
>      1.001023475         42,647,328      net_rx_drop
>      1.001023475        463,069,152      net_rx_errors
>      1.001023475                  0      net_rx_fifo
>      1.001023475                  0      net_rx_frame
>      1.001023475                  0      net_rx_multicast
>      1.001023475    423,195,831,744      net_rx_packets
>      1.001023475                  0      net_tx_bytes
>      1.001023475                  0      net_tx_carrier
>      1.001023475                  0      net_tx_colls
>      1.001023475                  0      net_tx_compressed
>      1.001023475                  0      net_tx_drop
>      1.001023475                  0      net_tx_errors
>      1.001023475                  0      net_tx_fifo
>      1.001023475                  0      net_tx_packets
> ```

Interesting.

> 
> As the events are in the tool_pmu they can be used in metrics. The
> json descriptions they are exposed in `perf list` and the events can
> be seen in the python ilist application.
> 
> Note, if a process terminates then the count reading returns an error
> and this can expose what appear to be latent bugs in the aggregation
> and display code.

How do you handle system-wide mode and sampling (perf record)?

Thanks,
Namhyung

> 
> Ian Rogers (2):
>   perf tool_pmu: Add memory events
>   perf tool_pmu: Add network events
> 
>  tools/perf/builtin-stat.c                     |  10 +-
>  .../pmu-events/arch/common/common/tool.json   | 266 ++++++++-
>  tools/perf/pmu-events/empty-pmu-events.c      | 312 +++++++----
>  tools/perf/util/tool_pmu.c                    | 514 +++++++++++++++++-
>  tools/perf/util/tool_pmu.h                    |  44 ++
>  5 files changed, 1026 insertions(+), 120 deletions(-)
> 
> -- 
> 2.52.0.351.gbe84eed79e-goog
> 

  parent reply	other threads:[~2026-01-07  8:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-04  1:17 [PATCH v1 0/2] Add procfs based memory and network tool events Ian Rogers
2026-01-04  1:17 ` [PATCH v1 1/2] perf tool_pmu: Add memory events Ian Rogers
2026-01-04  1:17 ` [PATCH v1 2/2] perf tool_pmu: Add network events Ian Rogers
2026-01-04  1:21 ` [PATCH v1 0/2] Add procfs based memory and network tool events Ian Rogers
2026-01-07  8:08 ` Namhyung Kim [this message]
2026-01-07 19:03   ` Ian Rogers
2026-01-12 16:50 ` Andi Kleen
2026-01-12 18:08   ` Ian Rogers
2026-01-15  5:00     ` Namhyung Kim

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=aV4UZCCc2QOhdeSE@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=thomas.falcon@intel.com \
    --cc=tmricht@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.