From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932441AbdJZOjQ (ORCPT ); Thu, 26 Oct 2017 10:39:16 -0400 Received: from mail-qt0-f169.google.com ([209.85.216.169]:57237 "EHLO mail-qt0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932255AbdJZOjM (ORCPT ); Thu, 26 Oct 2017 10:39:12 -0400 X-Google-Smtp-Source: ABhQp+TkSjxJLUgbQ+P0tQoIulNZOkUhmzPZwPegxHBYNP48rx/orR8PlsGuBk6Njb0mfuqCNt5gBQ== Date: Thu, 26 Oct 2017 07:39:08 -0700 From: Tejun Heo To: Waiman Long Cc: Li Zefan , Johannes Weiner , Jonathan Corbet , linux-kernel@vger.kernel.org, cgroups@vger.kernel.org, linux-doc@vger.kernel.org, Mike Galbraith , Christian Brauner , =?iso-8859-1?Q?St=E9phane?= Graber , Serge Hallyn Subject: Re: [PATCH v3] cpuset: Enable cpuset controller in default hierarchy Message-ID: <20171026143908.GD59538@devbig577.frc2.facebook.com> References: <1507324230-22996-1-git-send-email-longman@redhat.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 Hello, Waiman. On Wed, Oct 25, 2017 at 11:50:34AM -0400, Waiman Long wrote: > Ping! Any comment on this patch? Sorry about the lack of response. Here are my two thoughts. 1. I'm not really sure about the memory part. Mostly because of the way it's configured and enforced is completely out of step with how mm behaves in general. I'd like to get more input from mm folks on this. 2. I want to think more about how we expose the effective settings. Not that anything is wrong with what cpuset does, but more that I wanna ensure that it's something we can follow in other cases where we have similar hierarchical property propagation. We're likely too late for the coming merge window. Let's handle it during the next window. Thanks and my apologies for the delay. -- tejun