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 S1755845AbcJZReZ (ORCPT <rfc822;w@1wt.eu>);
        Wed, 26 Oct 2016 13:34:25 -0400
Received: from Galois.linutronix.de ([146.0.238.70]:41046 "EHLO
        Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1753809AbcJZReW (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 26 Oct 2016 13:34:22 -0400
Date: Wed, 26 Oct 2016 19:31:30 +0200 (CEST)
From: Thomas Gleixner <tglx@linutronix.de>
To: "Luck, Tony" <tony.luck@intel.com>
cc: "Yu, Fenghua" <fenghua.yu@intel.com>,
        "Anvin, H Peter" <h.peter.anvin@intel.com>,
        Ingo Molnar <mingo@elte.hu>, Peter Zijlstra <peterz@infradead.org>,
        Stephane Eranian <eranian@google.com>, Borislav Petkov <bp@suse.de>,
        "Hansen, Dave" <dave.hansen@intel.com>,
        Nilay Vaish <nilayvaish@gmail.com>, Shaohua Li <shli@fb.com>,
        David Carrillo-Cisneros <davidcc@google.com>,
        "Shankar, Ravi V" <ravi.v.shankar@intel.com>,
        "Prakhya, Sai Praneeth" <sai.praneeth.prakhya@intel.com>,
        Vikas Shivappa <vikas.shivappa@linux.intel.com>,
        linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>
Subject: Re: [PATCH v5 10/18] x86/intel_rdt: Build structures for each resource
 based on cache topology
In-Reply-To: <B982804C-D1AF-48AA-954F-9914BDB09BE5@intel.com>
Message-ID: <alpine.DEB.2.20.1610261930020.5013@nanos>
References: <1477142405-32078-1-git-send-email-fenghua.yu@intel.com> <1477142405-32078-11-git-send-email-fenghua.yu@intel.com>,<alpine.DEB.2.20.1610261451060.4983@nanos> <B982804C-D1AF-48AA-954F-9914BDB09BE5@intel.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 Wed, 26 Oct 2016, Luck, Tony wrote:

> Order is visible to users when we print entries in the schemata file, and
> validate input that they write (we require that they provide all masks in
> the same order as this list).

> If we hot remove a socket, it disappears from the list, and from the
> schemata file. When we put in a replacement it reappears. I didn't want
> the user to see:
> L3:0=fffff;2=fffff;3=fffff;1=fffff
> after hot replace socket 1, hence the sort.

Fair enough. Spelling this out in a comment might prevent questions about
this in the future.
 
Thanks,

	tglx