Peter Zijlstra writes:
> On Wed, Dec 14, 2016 at 08:56:43AM +1300, Eric W. Biederman wrote:
>>
>> I would just make the identifier a structure containing the
>> device number and the inode number. It didn't look like perf required
>> the identifier to be a simple integer.
Peter Zijlstra writes:
> On Wed, Dec 14, 2016 at 08:56:43AM +1300, Eric W. Biederman wrote:
>>
>> I would just make the identifier a structure containing the
>> device number and the inode number. It didn't look like perf required
>> the identifier to be a simple integer.
>
> Right, perf
On Wednesday 14 December 2016 09:22 PM, Eric W. Biederman wrote:
Peter Zijlstra writes:
On Wed, Dec 14, 2016 at 08:56:43AM +1300, Eric W. Biederman wrote:
I would just make the identifier a structure containing the
device number and the inode number. It didn't look
On Wednesday 14 December 2016 09:22 PM, Eric W. Biederman wrote:
Peter Zijlstra writes:
On Wed, Dec 14, 2016 at 08:56:43AM +1300, Eric W. Biederman wrote:
I would just make the identifier a structure containing the
device number and the inode number. It didn't look like perf required
the
On Wed, Dec 14, 2016 at 08:56:43AM +1300, Eric W. Biederman wrote:
>
> I would just make the identifier a structure containing the
> device number and the inode number. It didn't look like perf required
> the identifier to be a simple integer.
Right, perf doesn't care at all here, its just a
On Wed, Dec 14, 2016 at 08:56:43AM +1300, Eric W. Biederman wrote:
>
> I would just make the identifier a structure containing the
> device number and the inode number. It didn't look like perf required
> the identifier to be a simple integer.
Right, perf doesn't care at all here, its just a
Hari Bathini writes:
> Hi Eric,
>
>
> On Tuesday 13 December 2016 03:36 AM, Eric W. Biederman wrote:
>> Hari Bathini writes:
>>
>>> This patch introduces a cgroup identifier entry field in perf report to
>>> identify or distinguish data
Hari Bathini writes:
> Hi Eric,
>
>
> On Tuesday 13 December 2016 03:36 AM, Eric W. Biederman wrote:
>> Hari Bathini writes:
>>
>>> This patch introduces a cgroup identifier entry field in perf report to
>>> identify or distinguish data of different cgroups. It uses the unique
>>> inode number
Hi Eric,
On Tuesday 13 December 2016 03:36 AM, Eric W. Biederman wrote:
Hari Bathini writes:
This patch introduces a cgroup identifier entry field in perf report to
identify or distinguish data of different cgroups. It uses the unique
inode number of cgroup
Hi Eric,
On Tuesday 13 December 2016 03:36 AM, Eric W. Biederman wrote:
Hari Bathini writes:
This patch introduces a cgroup identifier entry field in perf report to
identify or distinguish data of different cgroups. It uses the unique
inode number of cgroup namespace, included in perf data
Hari Bathini writes:
> This patch introduces a cgroup identifier entry field in perf report to
> identify or distinguish data of different cgroups. It uses the unique
> inode number of cgroup namespace, included in perf data with the new
> PERF_RECORD_NAMESPACES
Hari Bathini writes:
> This patch introduces a cgroup identifier entry field in perf report to
> identify or distinguish data of different cgroups. It uses the unique
> inode number of cgroup namespace, included in perf data with the new
> PERF_RECORD_NAMESPACES event, as cgroup identifier. With
This patch introduces a cgroup identifier entry field in perf report to
identify or distinguish data of different cgroups. It uses the unique
inode number of cgroup namespace, included in perf data with the new
PERF_RECORD_NAMESPACES event, as cgroup identifier. With the assumption
that each
This patch introduces a cgroup identifier entry field in perf report to
identify or distinguish data of different cgroups. It uses the unique
inode number of cgroup namespace, included in perf data with the new
PERF_RECORD_NAMESPACES event, as cgroup identifier. With the assumption
that each
14 matches
Mail list logo