From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753225AbdHQSsu (ORCPT ); Thu, 17 Aug 2017 14:48:50 -0400 Received: from mail-qt0-f193.google.com ([209.85.216.193]:34371 "EHLO mail-qt0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752236AbdHQSst (ORCPT ); Thu, 17 Aug 2017 14:48:49 -0400 Date: Thu, 17 Aug 2017 11:48:44 -0700 From: Tejun Heo To: Waiman Long Cc: Li Zefan , Johannes Weiner , linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/2] cgroup: Add a hint to allow v1 controller to use v2 behavior Message-ID: <20170817184844.GB491396@devbig577.frc2.facebook.com> References: <1502994339-21668-1-git-send-email-longman@redhat.com> <1502994339-21668-2-git-send-email-longman@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1502994339-21668-2-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 Hello, Waiman. On Thu, Aug 17, 2017 at 02:25:38PM -0400, Waiman Long wrote: > For some cgroup controllers, the behavior on cgroup v1 differs somewhat > from cgroup v2. To indicate that a controller can use v2 behavior > in cgroup v1, a new cgroupfs mount option "v2_mode" is added. This > is essentially a hint, there is no obligation for a controller to > comply with this semantics. Heh, I don't think we can make it a generic flag. We can't have one kernel interpreting the option one way and later kernels doing differently. Let's just make it cpuset specific - something like cpuset_v2_mode. Thanks. -- tejun