Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753046AbdHXOn3 (ORCPT ); Thu, 24 Aug 2017 10:43:29 -0400 Received: from mail-qt0-f193.google.com ([209.85.216.193]:37890 "EHLO mail-qt0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751061AbdHXOn1 (ORCPT ); Thu, 24 Aug 2017 10:43:27 -0400 Date: Thu, 24 Aug 2017 07:43:22 -0700 From: Tejun Heo To: Waiman Long Cc: Li Zefan , Johannes Weiner , cgroups@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] cpuset: Allow cpuset controller in default hierarchy Message-ID: <20170824144322.GP491396@devbig577.frc2.facebook.com> References: <1503585611-13496-1-git-send-email-longman@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1503585611-13496-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: 508 Lines: 16 Hello, Waiman. On Thu, Aug 24, 2017 at 10:40:11AM -0400, Waiman Long wrote: > Given the fact that thread mode is now queued for 4.14, it is now > time to enable cpuset to be used in the default hierarchy (cgroup v2) > as it is clearly threaded. I'm not sure we want things like exclusive settings in v2 as it directly violates basic hierarchy rules (a sibling shouldn't be able to affect what another sibling can or can't do). We need to think more about what should be exposed in v2. Thanks. -- tejun