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 S932773AbcKPTD1 (ORCPT <rfc822;w@1wt.eu>);
        Wed, 16 Nov 2016 14:03:27 -0500
Received: from Galois.linutronix.de ([146.0.238.70]:46962 "EHLO
        Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S932201AbcKPTD0 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 16 Nov 2016 14:03:26 -0500
Date: Wed, 16 Nov 2016 20:00:44 +0100 (CET)
From: Thomas Gleixner <tglx@linutronix.de>
To: David Carrillo-Cisneros <davidcc@google.com>
cc: Peter Zijlstra <peterz@infradead.org>,
        linux-kernel <linux-kernel@vger.kernel.org>,
        "x86@kernel.org" <x86@kernel.org>, Ingo Molnar <mingo@redhat.com>,
        Andi Kleen <ak@linux.intel.com>, Kan Liang <kan.liang@intel.com>,
        Vegard Nossum <vegard.nossum@gmail.com>,
        Marcelo Tosatti <mtosatti@redhat.com>,
        Nilay Vaish <nilayvaish@gmail.com>, Borislav Petkov <bp@suse.de>,
        Vikas Shivappa <vikas.shivappa@linux.intel.com>,
        Ravi V Shankar <ravi.v.shankar@intel.com>,
        Fenghua Yu <fenghua.yu@intel.com>, Paul Turner <pjt@google.com>,
        Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH v3 05/46] perf/x86/intel/cmt: add per-package locks
In-Reply-To: <CALcN6mgq50P+KT__Mc2QpV9FUzCL5jtZPWfNaZfX-g3_xm28Cg@mail.gmail.com>
Message-ID: <alpine.DEB.2.20.1611161958170.3697@nanos>
References: <1477787923-61185-1-git-send-email-davidcc@google.com> <1477787923-61185-6-git-send-email-davidcc@google.com> <alpine.DEB.2.20.1611101619270.3501@nanos> <CALcN6miYhT1gVVOgMSLNCn9ksrRVZuXoiHUN-MCRKob1-JV-AA@mail.gmail.com>
 <20161111072156.GS3568@worktop.programming.kicks-ass.net> <CALcN6mgq50P+KT__Mc2QpV9FUzCL5jtZPWfNaZfX-g3_xm28Cg@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 Mon, 14 Nov 2016, David Carrillo-Cisneros wrote:

> > Also, "monr" is a horribly 'word'.
> 
> What makes it so bad? (honest question) . Some alternatives:
> 
> - res_mon, resm, rmon (Resource Monitor)
> - rmnode, rnode, rmon_node (Resource Monitoring node, similar to
> Resource Monitor ID, but to reflect that it's a node in a
> tree/hierarchy)
>  - rdt_mon, rdtm (something with RDT + Monitoring)
>  - ment, rdt_ment (Monitoring Entity)
> 
> Other suggestions?

The naming is the least of my worries right now. Before you start to rework
the series can we please get the information about:

    - what you want to achieve and why

    - the design of your approach

so we can avoid staring at another series of 40+ patches just to figure out
that something is wrong at the conceptual level?

We sort out the naming convention once we are done with the above.

Thanks,

	tglx