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 S1754266AbdASSpz (ORCPT <rfc822;w@1wt.eu>);
        Thu, 19 Jan 2017 13:45:55 -0500
Received: from Galois.linutronix.de ([146.0.238.70]:58152 "EHLO
        Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1754187AbdASSpy (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 19 Jan 2017 13:45:54 -0500
Date: Thu, 19 Jan 2017 18:54:25 +0100 (CET)
From: Thomas Gleixner <tglx@linutronix.de>
To: David Carrillo-Cisneros <davidcc@google.com>
cc: Shivappa Vikas <vikas.shivappa@intel.com>,
        Vikas Shivappa <vikas.shivappa@linux.intel.com>,
        Stephane Eranian <eranian@google.com>,
        linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>,
        hpa@zytor.com, Ingo Molnar <mingo@kernel.org>,
        Peter Zijlstra <peterz@infradead.org>,
        "Shankar, Ravi V" <ravi.v.shankar@intel.com>,
        "Luck, Tony" <tony.luck@intel.com>, Fenghua Yu <fenghua.yu@intel.com>,
        andi.kleen@intel.com, "H. Peter Anvin" <h.peter.anvin@intel.com>
Subject: Re: [PATCH 00/12] Cqm2: Intel Cache quality monitoring fixes
In-Reply-To: <CALcN6mgyXu2Ekqwi+MC24R1X5FVWvG7xcJZH8Ppjh+j+vgm2qg@mail.gmail.com>
Message-ID: <alpine.DEB.2.20.1701191851310.5358@nanos>
References: <1483740005-23499-1-git-send-email-vikas.shivappa@linux.intel.com> <alpine.DEB.2.20.1701171806220.3495@nanos> <alpine.DEB.2.10.1701171826180.15892@vshiva-Udesk> <alpine.DEB.2.20.1701180905130.3464@nanos> <CALcN6mhmVfTU3o4L1FuaAXdgtnXwEOW-tP=O_aLFfFGC9dX_Kw@mail.gmail.com>
 <CALcN6mgyXu2Ekqwi+MC24R1X5FVWvG7xcJZH8Ppjh+j+vgm2qg@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 Thu, 19 Jan 2017, David Carrillo-Cisneros wrote:
> A 1:1 mapping between CLOSID/"Resource group" to RMID, as Fenghua suggested
> is very problematic because the number of CLOSIDs is much much smaller than the
> number of RMIDs, and, as Stephane mentioned it's a common use case to want to
> independently monitor many task/cgroups inside an allocation partition.

Again, that was not my intention. I just want to limit the combinations.

> A 1:many mapping of CLOSID to RMIDs may work as a cheap replacement of
> cgroup monitoring but the case where CLOSID changes would be messy. In

CLOSIDs of RDT groups do not change. They are allocated when the group is
created.

Thanks,

	tglx