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 S933976AbdBQNmD (ORCPT <rfc822;w@1wt.eu>);
        Fri, 17 Feb 2017 08:42:03 -0500
Received: from Galois.linutronix.de ([146.0.238.70]:56724 "EHLO
        Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S933336AbdBQNmC (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 17 Feb 2017 08:42:02 -0500
Date: Fri, 17 Feb 2017 14:41:54 +0100 (CET)
From: Thomas Gleixner <tglx@linutronix.de>
To: Stephane Eranian <eranian@google.com>
cc: "Luck, Tony" <tony.luck@intel.com>,
        David Carrillo-Cisneros <davidcc@google.com>,
        Vikas Shivappa <vikas.shivappa@linux.intel.com>,
        "Shivappa, Vikas" <vikas.shivappa@intel.com>,
        linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>,
        "hpa@zytor.com" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>,
        Peter Zijlstra <peterz@infradead.org>,
        "Shankar, Ravi V" <ravi.v.shankar@intel.com>,
        "Yu, Fenghua" <fenghua.yu@intel.com>,
        "Kleen, Andi" <andi.kleen@intel.com>,
        "Anvin, H Peter" <h.peter.anvin@intel.com>
Subject: Re: [PATCH 00/12] Cqm2: Intel Cache quality monitoring fixes
In-Reply-To: <CABPqkBQW80CFY7PLjDO_EKRrr0TA+tu3zwoSU7tnL7DgdwV+Wg@mail.gmail.com>
Message-ID: <alpine.DEB.2.20.1702171300400.3536@nanos>
References: <alpine.DEB.2.20.1701201053350.3602@nanos> <CALcN6mjjAhinhKW_PtQhBNA6N3wLL=BkrrJ3oX5++M_cQuF-uQ@mail.gmail.com> <alpine.DEB.2.20.1701231013360.3836@nanos> <3908561D78D1C84285E8C5FCA982C28F3A2A8947@ORSMSX114.amr.corp.intel.com>
 <CALcN6mjYAaF2=2S_-afZz-iNM8NcoLEXFo5Mh30WJk=quaUTfA@mail.gmail.com> <3908561D78D1C84285E8C5FCA982C28F3A2A9CC7@ORSMSX114.amr.corp.intel.com> <CALcN6mhLz3B6w+o2ZFtG5PV1M-5Uz7o=34DN2U8uEW6xco+KSQ@mail.gmail.com> <20170202234100.GA17145@intel.com>
 <CALcN6mhh7ST0fs2K+dcCZBcGdYKyXD+Gvn7zhTbqH1Zn_hrp2Q@mail.gmail.com> <CALcN6mjbapHMjDttiq9A2kNfrOes55tFVoVWO9EMaPZuy+GwPA@mail.gmail.com> <20170203175220.GA15630@intel.com> <CABPqkBQW80CFY7PLjDO_EKRrr0TA+tu3zwoSU7tnL7DgdwV+Wg@mail.gmail.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
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 Feb 2017, Stephane Eranian wrote:
> 
> I think the design must ensure that the following usage models can be monitored:
>    - the allocations in your CAT partitions
>    - the allocations from a task (inclusive of children tasks)
>    - the allocations from a group of tasks (inclusive of children tasks)
>    - the allocations from a CPU
>    - the allocations from a group of CPUs

What's missing here is:

     - the allocations of a subset of users (tasks/groups/cpu(s)) of a
       particular CAT partition

Looking at your requirement list, all requirements, except the first point,
have no relationship to CAT (at least not from your write up). Now the
obvious questions are:

 - Does it make sense to ignore CAT relations in these sets?

 - Does it make sense to monitor a task / group of tasks, where the tasks
   belong to different CAT partitions?

 - Does it make sense to monitor a CPU / group of CPUs as a whole
   independent of which CAT partitions have been utilized during the
   monitoring period?

I don't think it makes any sense, unless the resulting information is split
up into CAT partitions.

I'm happy to be educated on the value of making this CAT unaware, but so
far I only came up with results, which need a crystal ball to analyze them.

Thanks,

	tglx