[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200109145355.GC61542@chrisdown.name>
Date: Thu, 9 Jan 2020 14:53:55 +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
>+ ONE("resctrl", S_IRUGO, proc_resctrl_show),
There was already some discussion about "resctrl" by itself being a misleading
name, hence why the CONFIG option eventually became CONFIG_X86_CPU_RESCTRL. Can
you please rethink the name of this /proc file, and have it at least be
"cpu_resctrl" or "x86_resctrl" or similar? :-)
Powered by blists - more mailing lists