Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp2450464ybl; Thu, 9 Jan 2020 13:01:23 -0800 (PST) X-Google-Smtp-Source: APXvYqzszhf5xFPvxVHdiNgNZRrAA37dyiLWCFhTACtIqTNk1vgRbCWAYU9VxLGeBuZsxuaiiGJn X-Received: by 2002:a9d:6b91:: with SMTP id b17mr10276036otq.321.1578603683818; Thu, 09 Jan 2020 13:01:23 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1578603683; cv=none; d=google.com; s=arc-20160816; b=VGmEP8hUZRZlQV7Uz5DXL0sUO13TlFdcnCZYnbfiyEZ5YRV1lUc/Z/xO6Q7EgnU7Mh x6eJp9AYpcQ0z8WX0AadVyMCW3GgEjeOximiW9X2CzRzLrxg7ZS7kPurxk044zHAuN3q ivOk2+aQGvYHHNwDHgsb8f/dNNxgmHUN1aHxC9c5khVuw2Drry7VgW6TggiIMaJ6e4hZ wi0s4Bv5RXpnt90bJEcvg6i1F9GrJx3yIzjF5xwEDpqjwo9WRTk5rFzAuNo9U+EH75SD c/H8yvCQMk5KsYOTZLrUGQfj87Ns0jS7aFeVDNfOIaECKi3L/SBCrjLYJTZeQwjrX0jr CCGA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=vALvPfYX0Ht+QpLWxzMOlZSL2wHrm1aVhbN/Qh29nM8=; b=wzydPrsRL/h7lVrdu3Wr5RanPGHJVh+KGflRnEoK3oLOk9h3Fvyeoe2W8EMlS1kUAd smXBawQAK/ec5EXKEzbhQjD28M3B1YbsZuntxee3h8NTfDQNACh0o12GJ8DDg1KebcYZ mZfAX3Hq1U4ao3zgevNiVVI628L5Y3/fyy5oMfRIY1KyQvdu0kTORTgUg6QYpQODwyd/ v9EcJN4ewJqPddNU94nNQ52unTE/A43l8x0PTc2japYii6zanSXckk1afhjm3VWCv1gd S6BaHiuzIJ/F7cok+FfdAeSqgFEj9uHYPmhDDWZ8Cg/a38tEp4/G0fde244bTc0XENkH wcIw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 5si4165723oiy.102.2020.01.09.13.01.11; Thu, 09 Jan 2020 13:01:23 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388284AbgAIRqx (ORCPT + 99 others); Thu, 9 Jan 2020 12:46:53 -0500 Received: from mga03.intel.com ([134.134.136.65]:13542 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731838AbgAIRqw (ORCPT ); Thu, 9 Jan 2020 12:46:52 -0500 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Jan 2020 09:46:52 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,414,1571727600"; d="scan'208";a="396165253" Received: from chenyu-office.sh.intel.com ([10.239.158.173]) by orsmga005.jf.intel.com with ESMTP; 09 Jan 2020 09:46:49 -0800 Date: Fri, 10 Jan 2020 01:45:45 +0800 From: Yu Chen To: Chris Down Cc: x86@kernel.org, Thomas Gleixner , Borislav Petkov , Ingo Molnar , "H. Peter Anvin" , Alexey Dobriyan , Andrew Morton , Reinette Chatre , Fenghua Yu , Tony Luck , Michal Hocko , Linus Torvalds , linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH][RESEND v5] x86/resctrl: Add task resctrl information display Message-ID: <20200109174544.GC11490@chenyu-office.sh.intel.com> References: <20200109135001.10076-1-yu.c.chen@intel.com> <20200109142444.GB61542@chrisdown.name> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200109142444.GB61542@chrisdown.name> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Chris, On Thu, Jan 09, 2020 at 02:24:44PM +0000, Chris Down wrote: > Chen Yu writes: > > +#ifdef CONFIG_PROC_CPU_RESCTRL > > + > > +/* > > + * A task can only be part of one control > > + * group and of one monitoring group which > > + * is associated to that control group. > > + * So one line is simple and clear enough: > > Can we please avoid using the word "control group" to describe these? It's > extremely confusing for readers since it's exactly the same word as used for > actual cgroups, especially since those are also a form of "resource > control"... > > Doesn't official documentation refer to them as "resource groups" to avoid > this? Right, how abut changing change this description to: control group -> resctrl allocation group monitor group -> resctrl monitor group? Yes, the Documentation/x86/resctrl_ui.rst described them as "Resource Control feature", which is composed of allocation and monitor, so distinguish them as above seems to be appropriate. Thanks, Chenyu