Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751679AbdHPOgd (ORCPT ); Wed, 16 Aug 2017 10:36:33 -0400 Received: from mail-qt0-f196.google.com ([209.85.216.196]:34166 "EHLO mail-qt0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751089AbdHPOgb (ORCPT ); Wed, 16 Aug 2017 10:36:31 -0400 Date: Wed, 16 Aug 2017 07:36:26 -0700 From: Tejun Heo To: Waiman Long Cc: Li Zefan , Johannes Weiner , Jonathan Corbet , linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [PATCH] cpuset: Allow v2 behavior in v1 cgroup Message-ID: <20170816143625.GD4087514@devbig577.frc2.facebook.com> References: <1502818040-9967-1-git-send-email-longman@redhat.com> <20170816142926.GC4087514@devbig577.frc2.facebook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 504 Lines: 17 Hello, On Wed, Aug 16, 2017 at 10:34:05AM -0400, Waiman Long wrote: > > It feels weird to make this a kernel boot param when all other options > > are specified on mount time. Is there a reason why this can't be a > > mount option too? > > > Yes, we can certainly make this a mount option instead of a boot time > parameter. BTW, where do we usually document the mount options for cgroup? I don't think there's a central place. Each controller documents theirs in their own file. Thanks. -- tejun