Re: [PATCH v2 1/2] perf: add container identifier entry in perf sample data

2016-09-02 Thread Hari Bathini
On Friday 02 September 2016 07:29 PM, Peter Zijlstra wrote: On Fri, Sep 02, 2016 at 07:25:31PM +0530, Hari Bathini wrote: I'm thinking this value is mostly the same for tasks, just like COMM and I think so, too. Namespaces aren't changed that often for tasks... MMAP. Could we therefore not

Re: [PATCH v2 1/2] perf: add container identifier entry in perf sample data

2016-09-02 Thread Hari Bathini
On Friday 02 September 2016 07:29 PM, Peter Zijlstra wrote: On Fri, Sep 02, 2016 at 07:25:31PM +0530, Hari Bathini wrote: I'm thinking this value is mostly the same for tasks, just like COMM and I think so, too. Namespaces aren't changed that often for tasks... MMAP. Could we therefore not

Re: [PATCH v2 1/2] perf: add container identifier entry in perf sample data

2016-09-02 Thread Peter Zijlstra
On Fri, Sep 02, 2016 at 07:25:31PM +0530, Hari Bathini wrote: > >I'm thinking this value is mostly the same for tasks, just like COMM and > > I think so, too. Namespaces aren't changed that often for tasks... > > >MMAP. Could we therefore not emit (sideband) events whenever a task > >changes

Re: [PATCH v2 1/2] perf: add container identifier entry in perf sample data

2016-09-02 Thread Peter Zijlstra
On Fri, Sep 02, 2016 at 07:25:31PM +0530, Hari Bathini wrote: > >I'm thinking this value is mostly the same for tasks, just like COMM and > > I think so, too. Namespaces aren't changed that often for tasks... > > >MMAP. Could we therefore not emit (sideband) events whenever a task > >changes

Re: [PATCH v2 1/2] perf: add container identifier entry in perf sample data

2016-09-02 Thread Hari Bathini
On Thursday 01 September 2016 02:39 PM, Peter Zijlstra wrote: On Tue, Aug 30, 2016 at 09:57:02PM +0530, Hari Bathini wrote: Currently, there is no mechanism to filter events based on containers. perf -G can be used, but it will not filter events for the containers created after perf is

Re: [PATCH v2 1/2] perf: add container identifier entry in perf sample data

2016-09-02 Thread Hari Bathini
On Thursday 01 September 2016 02:39 PM, Peter Zijlstra wrote: On Tue, Aug 30, 2016 at 09:57:02PM +0530, Hari Bathini wrote: Currently, there is no mechanism to filter events based on containers. perf -G can be used, but it will not filter events for the containers created after perf is

Re: [PATCH v2 1/2] perf: add container identifier entry in perf sample data

2016-09-01 Thread Peter Zijlstra
On Tue, Aug 30, 2016 at 09:57:02PM +0530, Hari Bathini wrote: > Currently, there is no mechanism to filter 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

Re: [PATCH v2 1/2] perf: add container identifier entry in perf sample data

2016-09-01 Thread Peter Zijlstra
On Tue, Aug 30, 2016 at 09:57:02PM +0530, Hari Bathini wrote: > Currently, there is no mechanism to filter 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

[PATCH v2 1/2] perf: add container identifier entry in perf sample data

2016-08-30 Thread Hari Bathini
Currently, there is no mechanism to filter 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 limitation can be overcome, if

[PATCH v2 1/2] perf: add container identifier entry in perf sample data

2016-08-30 Thread Hari Bathini
Currently, there is no mechanism to filter 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 limitation can be overcome, if