[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200109142444.GB61542@chrisdown.name>
Date: Thu, 9 Jan 2020 14:24:44 +0000
From: Chris Down <chris@...isdown.name>
To: Chen Yu <yu.c.chen@...el.com>
Cc: x86@...nel.org, Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>, Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Alexey Dobriyan <adobriyan@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Reinette Chatre <reinette.chatre@...el.com>,
Fenghua Yu <fenghua.yu@...el.com>,
Tony Luck <tony.luck@...el.com>,
Michal Hocko <mhocko@...e.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-fsdevel@...r.kernel.org, linux-api@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH][RESEND v5] x86/resctrl: Add task resctrl information
display
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?
Powered by blists - more mailing lists