public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Hari Bathini <hbathini@linux.vnet.ibm.com>
Cc: ast@fb.com, peterz@infradead.org,
	lkml <linux-kernel@vger.kernel.org>,
	acme@kernel.org, alexander.shishkin@linux.intel.com,
	mingo@redhat.com, daniel@iogearbox.net, rostedt@goodmis.org,
	Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>,
	sargun@sargun.me, Aravinda Prasad <aravinda@linux.vnet.ibm.com>,
	brendan.d.gregg@gmail.com, jolsa@redhat.com
Subject: Re: [PATCH v6 0/3] perf: add support for analyzing events for containers
Date: Thu, 16 Feb 2017 19:20:11 +1300	[thread overview]
Message-ID: <87zihm1wtg.fsf@xmission.com> (raw)
In-Reply-To: <148654265580.27983.8822211570127163843.stgit@hbathini.in.ibm.com> (Hari Bathini's message of "Wed, 08 Feb 2017 14:01:19 +0530")

Hari Bathini <hbathini@linux.vnet.ibm.com> writes:

> Currently, there is no trivial mechanism to analyze events based on
> containers. perf -G can be used, but it will not filter events for the
> containers created after perf is invoked, making it difficult to assess/
> analyze performance issues of multiple containers at once.
>
> This patch-set is aimed at addressing this limitation by introducing a
> new PERF_RECORD_NAMESPACES event that records namespaces related info.
> As containers are created with namespaces, the new data can be used to
> in assessment/analysis of multiple containers.
>
> The first patch introduces PERF_RECORD_NAMESPACES in kernel while the
> second patch makes the corresponding changes in perf tool to read this
> PERF_RECORD_NAMESPACES events. The third patch demonstrates analysis
> of containers with this data by adding a cgroup identifier column in
> perf report, which contains the cgroup namespace's device and inode
> numbers. This is based on the assumption that each container is created
> with it's own cgroup namespace. The third patch has scope for improvement
> based on the conventions a container is attributed with, going
> forward.

Ack for the namespace interface bits.
Everything I asked for is in there.

Eric


>
> Changes from v5:
> * Updated changelogs of patches 1 & 3
> * Rebased the patches on perf/core in tip
>
> ---
>
> Hari Bathini (3):
>       perf: add PERF_RECORD_NAMESPACES to include namespaces related info
>       perf tool: add PERF_RECORD_NAMESPACES to include namespaces related info
>       perf tool: add cgroup identifier entry in perf report
>
>
>  include/linux/perf_event.h            |    2 
>  include/uapi/linux/perf_event.h       |   38 +++++++++
>  kernel/events/core.c                  |  142 +++++++++++++++++++++++++++++++++
>  kernel/fork.c                         |    3 +
>  kernel/nsproxy.c                      |    5 +
>  tools/include/uapi/linux/perf_event.h |   38 +++++++++
>  tools/perf/builtin-annotate.c         |    1 
>  tools/perf/builtin-diff.c             |    1 
>  tools/perf/builtin-inject.c           |   14 +++
>  tools/perf/builtin-kmem.c             |    1 
>  tools/perf/builtin-kvm.c              |    2 
>  tools/perf/builtin-lock.c             |    1 
>  tools/perf/builtin-mem.c              |    1 
>  tools/perf/builtin-record.c           |   33 +++++++-
>  tools/perf/builtin-report.c           |    1 
>  tools/perf/builtin-sched.c            |    1 
>  tools/perf/builtin-script.c           |   41 +++++++++
>  tools/perf/builtin-trace.c            |    3 -
>  tools/perf/perf.h                     |    1 
>  tools/perf/util/Build                 |    1 
>  tools/perf/util/data-convert-bt.c     |    2 
>  tools/perf/util/event.c               |  143 ++++++++++++++++++++++++++++++++-
>  tools/perf/util/event.h               |   19 ++++
>  tools/perf/util/evsel.c               |    3 +
>  tools/perf/util/hist.c                |    7 ++
>  tools/perf/util/hist.h                |    1 
>  tools/perf/util/machine.c             |   34 ++++++++
>  tools/perf/util/machine.h             |    3 +
>  tools/perf/util/namespaces.c          |   35 ++++++++
>  tools/perf/util/namespaces.h          |   26 ++++++
>  tools/perf/util/session.c             |    7 ++
>  tools/perf/util/sort.c                |   41 +++++++++
>  tools/perf/util/sort.h                |    7 ++
>  tools/perf/util/thread.c              |   44 ++++++++++
>  tools/perf/util/thread.h              |    6 +
>  tools/perf/util/tool.h                |    2 
>  36 files changed, 695 insertions(+), 15 deletions(-)
>  create mode 100644 tools/perf/util/namespaces.c
>  create mode 100644 tools/perf/util/namespaces.h
>
> --

      parent reply	other threads:[~2017-02-16  6:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08  8:31 [PATCH v6 0/3] perf: add support for analyzing events for containers Hari Bathini
2017-02-08  8:31 ` [PATCH v6 1/3] perf: add PERF_RECORD_NAMESPACES to include namespaces related info Hari Bathini
2017-02-16 10:28   ` Peter Zijlstra
2017-02-16 10:36     ` Peter Zijlstra
2017-02-20  4:11     ` Hari Bathini
2017-02-16 11:25   ` Eric W. Biederman
2017-02-16 11:47     ` Peter Zijlstra
2017-02-20  4:16     ` Hari Bathini
2017-02-08  8:31 ` [PATCH v6 2/3] perf tool: " Hari Bathini
2017-02-08 12:57   ` Jiri Olsa
2017-02-08 12:57   ` Jiri Olsa
2017-02-08 12:57   ` Jiri Olsa
2017-02-21 14:03     ` Hari Bathini
2017-02-08  8:32 ` [PATCH v6 3/3] perf tool: add cgroup identifier entry in perf report Hari Bathini
2017-02-16  6:20 ` Eric W. Biederman [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=87zihm1wtg.fsf@xmission.com \
    --to=ebiederm@xmission.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=ananth@linux.vnet.ibm.com \
    --cc=aravinda@linux.vnet.ibm.com \
    --cc=ast@fb.com \
    --cc=brendan.d.gregg@gmail.com \
    --cc=daniel@iogearbox.net \
    --cc=hbathini@linux.vnet.ibm.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sargun@sargun.me \
    /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