From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S933273AbdCHAK6 (ORCPT <rfc822;w@1wt.eu>);
        Tue, 7 Mar 2017 19:10:58 -0500
Received: from mga04.intel.com ([192.55.52.120]:7736 "EHLO mga04.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1756511AbdCHAKh (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 7 Mar 2017 19:10:37 -0500
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.36,260,1486454400"; 
   d="scan'208";a="941771496"
Date: Tue, 7 Mar 2017 15:31:49 -0800 (PST)
From: Shivappa Vikas <vikas.shivappa@intel.com>
X-X-Sender: vikas@vshiva-Udesk
To: Stephane Eranian <eranian@google.com>
cc: "Luck, Tony" <tony.luck@intel.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        Vikas Shivappa <vikas.shivappa@linux.intel.com>,
        "Shivappa, Vikas" <vikas.shivappa@intel.com>,
        "x86@kernel.org" <x86@kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "hpa@zytor.com" <hpa@zytor.com>, "mingo@kernel.org" <mingo@kernel.org>,
        "peterz@infradead.org" <peterz@infradead.org>,
        "Shankar, Ravi V" <ravi.v.shankar@intel.com>,
        "Yu, Fenghua" <fenghua.yu@intel.com>,
        "Kleen, Andi" <andi.kleen@intel.com>,
        "davidcc@google.com" <davidcc@google.com>
Subject: Re: [PATCH 1/1] x86/cqm: Cqm requirements
In-Reply-To: <CABPqkBQaOt3_0EN+6D8sJ4erA6dFW-P7ECCgdWu6UxFaaJ-eyg@mail.gmail.com>
Message-ID: <alpine.DEB.2.10.1703071531140.5245@vshiva-Udesk>
References: <1488908964-30261-1-git-send-email-vikas.shivappa@linux.intel.com> <alpine.DEB.2.20.1703072011080.4299@nanos> <3908561D78D1C84285E8C5FCA982C28F6120F0A9@ORSMSX113.amr.corp.intel.com>
 <CABPqkBQaOt3_0EN+6D8sJ4erA6dFW-P7ECCgdWu6UxFaaJ-eyg@mail.gmail.com>
User-Agent: Alpine 2.10 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org



On Tue, 7 Mar 2017, Stephane Eranian wrote:

> Hi,
>
> On Tue, Mar 7, 2017 at 12:04 PM, Luck, Tony <tony.luck@intel.com> wrote:
>>> That's all nice and good, but I still have no coherent explanation why
>>> measuring across allocation domains makes sense.
>>
>> Is this in reaction to this one?
>>
>>>> 5)      Put multiple threads into a single measurement group
>>
>> If we fix it to say "threads from the same CAT group" does it fix things?
>>
> Inside a CAT partition, there may be multiple tasks split into
> different cgroups.
> We need the ability to monitor groups of tasks individually within that CAT
> partition. I think this is what this bullet is about.
>

The #8 covers that I think (or what we intended for 5..) ?

8)      Can get measurements for subsets of tasks in a CAT group (to find the
threads hogging the resources).

Thanks,
Vikas

>
>> We'd like to have measurement groups use a single RMID ... if we
>> allowed tasks from different CAT groups in the same measurement
>> group we wouldn't be able to split the numbers back to report the
>> right overall total for each of the CAT groups.
>>
>> -Tony
>