Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752450AbdHPO3d (ORCPT ); Wed, 16 Aug 2017 10:29:33 -0400 Received: from mail-qk0-f193.google.com ([209.85.220.193]:34263 "EHLO mail-qk0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751637AbdHPO3c (ORCPT ); Wed, 16 Aug 2017 10:29:32 -0400 Date: Wed, 16 Aug 2017 07:29:27 -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: <20170816142926.GC4087514@devbig577.frc2.facebook.com> References: <1502818040-9967-1-git-send-email-longman@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1502818040-9967-1-git-send-email-longman@redhat.com> 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: 563 Lines: 19 Hello, Waiman. On Tue, Aug 15, 2017 at 01:27:20PM -0400, Waiman Long wrote: > + cpuset_v2_mode= [KNL] Enable cpuset v2 behavior in cpuset v1 cgroups. > + In v2 mode, the cpus and mems can be restored to > + their original values after a removal-addition > + event sequence. > + 0: default value, cpuset v1 keeps legacy behavior. > + 1: cpuset v1 behaves like cpuset v2. > + 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? Thanks. -- tejun