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: Fri, 20 Jan 2017 17:54:07 +0100 [thread overview]
Message-ID: <20170120165407.GS6485@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <4019acf2-357d-af5d-a44c-414128e3033c@linux.vnet.ibm.com>
On Fri, Jan 20, 2017 at 09:26:32PM +0530, Hari Bathini wrote:
> Hi Peter,
>
>
> On Wednesday 18 January 2017 07:56 PM, Peter Zijlstra wrote:
> >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
>
> IIUC, Eric wanted to have device info saved for each namespace separately
> to avoid the need for a namespace of namespaces in future.
>
> >brought up. Where are we on that, and or why isn't it required?
>
>
> I did address that in v4 and haven't changed it in v5.
> I am not sure if it needs any mentioning in the changelog..
I would certainly have liked mention of the issue and its (non)
solution. It shows we thought about it and will help our older selves
remember.
next prev parent reply other threads:[~2017-01-20 16:55 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
2017-01-20 15:56 ` Hari Bathini
2017-01-20 16:54 ` Peter Zijlstra [this message]
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=20170120165407.GS6485@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).