From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk0-f198.google.com (mail-qk0-f198.google.com [209.85.220.198]) by kanga.kvack.org (Postfix) with ESMTP id 193A9831F4 for ; Thu, 18 May 2017 11:52:23 -0400 (EDT) Received: by mail-qk0-f198.google.com with SMTP id c75so17130983qka.7 for ; Thu, 18 May 2017 08:52:23 -0700 (PDT) Received: from mx1.redhat.com (mx1.redhat.com. [209.132.183.28]) by mx.google.com with ESMTPS id k187si5931802qke.86.2017.05.18.08.52.21 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 18 May 2017 08:52:22 -0700 (PDT) Subject: Re: [RFC PATCH v2 08/17] cgroup: Move debug cgroup to its own file References: <1494855256-12558-1-git-send-email-longman@redhat.com> <1494855256-12558-9-git-send-email-longman@redhat.com> <20170517213603.GE942@htj.duckdns.org> From: Waiman Long Message-ID: Date: Thu, 18 May 2017 11:52:18 -0400 MIME-Version: 1.0 In-Reply-To: <20170517213603.GE942@htj.duckdns.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Tejun Heo Cc: Li Zefan , Johannes Weiner , Peter Zijlstra , Ingo Molnar , cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-mm@kvack.org, kernel-team@fb.com, pjt@google.com, luto@amacapital.net, efault@gmx.de On 05/17/2017 05:36 PM, Tejun Heo wrote: > Hello, Waiman. > > On Mon, May 15, 2017 at 09:34:07AM -0400, Waiman Long wrote: >> The debug cgroup currently resides within cgroup-v1.c and is enabled >> only for v1 cgroup. To enable the debug cgroup also for v2, it >> makes sense to put the code into its own file as it will no longer >> be v1 specific. The only change in this patch is the expansion of >> cgroup_task_count() within the debug_taskcount_read() function. >> >> Signed-off-by: Waiman Long > I don't mind enabling the debug controller for v2 but let's please > hide it behind an unwieldy boot param / controller name so that it's > clear that its interface isn't expected to be stable. > > Thanks. > The controller name is "debug" and so it is obvious what this controller is for. However, the config prompt "Example controller" is indeed vague in meaning. So we can make the prompt more descriptive here. As for the boot param, are you saying something like "cgroup_debug" has to be specified in the command line even if CGROUP_DEBUG config is there for the debug controller to be enabled? I am fine with that if you think it is necessary. Regards, Longman -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org