Aravinda Prasad writes:
> On Wednesday 04 January 2017 02:34 PM, Krister Johansen wrote:
>> On Tue, Jan 03, 2017 at 04:57:54PM +0530, Hari Bathini wrote:
>>> On Thursday 29 December 2016 07:11 AM, Krister Johansen wrote:
On Fri, Dec 16, 2016 at 12:06:55AM +0530, Hari Bathini wrote:
> Thi
On Wednesday 04 January 2017 02:34 PM, Krister Johansen wrote:
> On Tue, Jan 03, 2017 at 04:57:54PM +0530, Hari Bathini wrote:
>> On Thursday 29 December 2016 07:11 AM, Krister Johansen wrote:
>>> On Fri, Dec 16, 2016 at 12:06:55AM +0530, Hari Bathini wrote:
This patch-set overcomes this lim
On Wednesday 04 January 2017 02:34 PM, Krister Johansen wrote:
On Tue, Jan 03, 2017 at 04:57:54PM +0530, Hari Bathini wrote:
On Thursday 29 December 2016 07:11 AM, Krister Johansen wrote:
On Fri, Dec 16, 2016 at 12:06:55AM +0530, Hari Bathini wrote:
This patch-set overcomes this limitation b
On Tue, Jan 03, 2017 at 04:57:54PM +0530, Hari Bathini wrote:
> On Thursday 29 December 2016 07:11 AM, Krister Johansen wrote:
> >On Fri, Dec 16, 2016 at 12:06:55AM +0530, Hari Bathini wrote:
> >>This patch-set overcomes this limitation by using cgroup identifier as
> >>container unique identifier.
Hi Krister,
Thanks for reviewing..
On Thursday 29 December 2016 07:11 AM, Krister Johansen wrote:
On Fri, Dec 16, 2016 at 12:06:55AM +0530, Hari Bathini wrote:
This patch-set overcomes this limitation by using cgroup identifier as
container unique identifier. A new PERF_RECORD_NAMESPACES even
On Fri, Dec 16, 2016 at 12:06:55AM +0530, Hari Bathini wrote:
> This patch-set overcomes this limitation by using cgroup identifier as
> container unique identifier. A new PERF_RECORD_NAMESPACES event that
> records namespaces related info is introduced, from which the cgroup
> namespace's device &
Hi Alban,
On Friday 16 December 2016 05:44 PM, Alban Crequy wrote:
Hi,
Currently, there is no trivial mechanism to analyze 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 pe
Hi,
> Currently, there is no trivial mechanism to analyze 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 patch-
Currently, there is no trivial mechanism to analyze 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 patch-set overcomes th
9 matches
Mail list logo