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
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 name
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 invoked
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
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 th
5 matches
Mail list logo