From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Andi Kleen <ak@linux.intel.com>,
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, 14 Jan 2026 21:00:15 -0800 [thread overview]
Message-ID: <aWh0XwBDZRRYcZOG@google.com> (raw)
In-Reply-To: <CAP-5=fW0QQj08_S+nn5+kos1mzMbeNg9EBeKPKm03Gfqj80v+A@mail.gmail.com>
On Mon, Jan 12, 2026 at 10:08:20AM -0800, Ian Rogers wrote:
> On Mon, Jan 12, 2026 at 8:51 AM Andi Kleen <ak@linux.intel.com> wrote:
> >
> > Ian Rogers <irogers@google.com> writes:
> >
> > > 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
> >
> > But AFAIK that's for the complete network name space, not just the
> > process, thus highly misleading in perf context because the scope
> > is incompatible.
>
> Yeah, we can point this out in the event descriptions or just not have
> the events and try to do some per process BPF type thing. Given we
> don't have the BPF thing it is still tempting to have these counters
> as-is for the system-wide case.
You may want to make it fail to open for per-process mode.
Thanks,
Namhyung
prev parent reply other threads:[~2026-01-15 5:00 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
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 [this message]
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=aWh0XwBDZRRYcZOG@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox