From: Peter Zijlstra <peterz@infradead.org>
To: Hari Bathini <hbathini@linux.vnet.ibm.com>
Cc: ast@fb.com, 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>,
ebiederm@xmission.com, sargun@sargun.me,
Aravinda Prasad <aravinda@linux.vnet.ibm.com>,
brendan.d.gregg@gmail.com, jolsa@redhat.com
Subject: Re: [PATCH v5 1/3] perf: add PERF_RECORD_NAMESPACES to include namespaces related info
Date: Wed, 18 Jan 2017 15:26:08 +0100 [thread overview]
Message-ID: <20170118142608.GF6515@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <148466262903.32153.14129217679474433212.stgit@hbathini.in.ibm.com>
On Tue, Jan 17, 2017 at 07:47:22PM +0530, Hari Bathini wrote:
> With the advert of container technologies like docker, that depend
> on namespaces for isolation, there is a need for tracing support for
> namespaces. This patch introduces new PERF_RECORD_NAMESPACES event
> for tracing based on namespaces related info.
This fails to mention the whole namespace of namespaces issue Eric
brought up. Where are we on that, and or why isn't it required?
> +/*
> + * The maximum size of the name of each namespace
> + */
> +#define NS_NAME_SIZE 8
> +
> +struct perf_ns_link_info {
> + char name[NS_NAME_SIZE];
Do we really need a name? why?
> + __u64 dev;
> + __u64 ino;
> +};
> +
next prev parent reply other threads:[~2017-01-18 14:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 14:16 [PATCH v5 0/3] perf: add support for analyzing events for containers Hari Bathini
2017-01-17 14:17 ` [PATCH v5 1/3] perf: add PERF_RECORD_NAMESPACES to include namespaces related info Hari Bathini
2017-01-18 14:26 ` Peter Zijlstra [this message]
2017-01-20 15:56 ` Hari Bathini
2017-01-20 16:54 ` Peter Zijlstra
2017-01-17 14:17 ` [PATCH v5 2/3] perf tool: " Hari Bathini
2017-01-18 13:14 ` Jiri Olsa
2017-01-17 14:18 ` [PATCH v5 3/3] perf tool: add cgroup identifier entry in perf report Hari Bathini
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=20170118142608.GF6515@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--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=ebiederm@xmission.com \
--cc=hbathini@linux.vnet.ibm.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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 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.