From: Hari Bathini <hbathini@linux.vnet.ibm.com>
To: "Eric W. Biederman" <ebiederm@xmission.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 1/3] perf: add PERF_RECORD_NAMESPACES to include namespaces related info
Date: Mon, 20 Feb 2017 09:46:03 +0530 [thread overview]
Message-ID: <45ec7ff8-cddf-56a5-95da-0e46cfb21b60@linux.vnet.ibm.com> (raw)
In-Reply-To: <87zihmtm1k.fsf@xmission.com>
Hi Eric,
On Thursday 16 February 2017 04:55 PM, Eric W. Biederman wrote:
>> +/*
>> + * The maximum size of the name of each namespace
>> + */
>> +#define NS_NAME_SIZE 8
>> +
>> +struct perf_ns_link_info {
>> + char name[NS_NAME_SIZE];
>> + __u64 dev;
>> + __u64 ino;
>> +};
> Ugh. I missed the name the first time around.
>
> That really looks like useless clutter. You already know the index so
> the name doesn't add any information, so unless I am missing something
> that name will just slow down the perf kernel implementation with
> useless work.
>
> The userspace reader can have the information just as reliably by
> looking at the index and indexing into a table.
>
> The set of namespaces changes slowly enough that this is not likely to
> be a problem in practice. Especially as perf is released with the
> kernel.
>
> Plus who knows how long the name of the next namespace is going to be.
>
Agreed. Will drop name field from the structure and use an indexing
table to get names in userspace..
Thanks
Hari
next prev parent reply other threads:[~2017-02-20 6:25 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 [this message]
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 ` [PATCH v6 0/3] perf: add support for analyzing events for containers Eric W. Biederman
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=45ec7ff8-cddf-56a5-95da-0e46cfb21b60@linux.vnet.ibm.com \
--to=hbathini@linux.vnet.ibm.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=ebiederm@xmission.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
all inboxes | Powered by JetHome®