Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935199AbdCJKzY (ORCPT ); Fri, 10 Mar 2017 05:55:24 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:55418 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934951AbdCJKzV (ORCPT ); Fri, 10 Mar 2017 05:55:21 -0500 Date: Fri, 10 Mar 2017 11:53:45 +0100 (CET) From: Thomas Gleixner To: Shivappa Vikas cc: vikas.shivappa@intel.com, linux-kernel@vger.kernel.org, x86@kernel.org, hpa@zytor.com, mingo@kernel.org, peterz@infradead.org, ravi.v.shankar@intel.com, tony.luck@intel.com, fenghua.yu@intel.com, andi.kleen@intel.com Subject: Re: [PATCH 2/5] x86/intel_rdt: Improvements to parsing schemata In-Reply-To: Message-ID: References: <1487360328-6768-1-git-send-email-vikas.shivappa@linux.intel.com> <1487360328-6768-3-git-send-email-vikas.shivappa@linux.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: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 747 Lines: 22 On Thu, 9 Mar 2017, Shivappa Vikas wrote: > > > Anyway, first of all we want to know WHY this ordering is required. If it's > > not required then why would we enforce it? > > Do the users want to see the data in the same order they entered ? If we want > to do that then its easy to implement when we enforce the order .. (because > right now resources are always displayed in a predefined order). > Otherwise i can drop this patch. It's fine to display them in a defined order, but there is no point to enforce the ordering on write. The real question here is whether we really have to write every line on every update. IMO it's sufficient to write a single resource line and not require to update all resources every time. Thanks, tglx