[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87k2b233up.fsf@xmission.com>
Date: Thu, 15 Dec 2016 04:52:30 +1300
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Peter Zijlstra <peterz@...radead.org>
Cc: Hari Bathini <hbathini@...ux.vnet.ibm.com>, ast@...com,
lkml <linux-kernel@...r.kernel.org>, acme@...nel.org,
alexander.shishkin@...ux.intel.com, mingo@...hat.com,
daniel@...earbox.net, rostedt@...dmis.org,
Ananth N Mavinakayanahalli <ananth@...ux.vnet.ibm.com>,
sargun@...gun.me, Aravinda Prasad <aravinda@...ux.vnet.ibm.com>,
brendan.d.gregg@...il.com
Subject: Re: [PATCH v3 3/3] perf tool: add cgroup identifier entry in perf report
Peter Zijlstra <peterz@...radead.org> 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 doesn't care at all here, its just a transport.
perf report? In that case I think perf cares enough to know there is
some identifier it is reporting things by.
Eric
Powered by blists - more mailing lists