From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752159AbeC0OXo convert rfc822-to-8bit (ORCPT ); Tue, 27 Mar 2018 10:23:44 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:53272 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751292AbeC0OXi (ORCPT ); Tue, 27 Mar 2018 10:23:38 -0400 Subject: Re: [PATCH v6 2/2] cpuset: Add cpuset.sched_load_balance to v2 To: Tejun Heo Cc: Juri Lelli , Li Zefan , Johannes Weiner , Peter Zijlstra , Ingo Molnar , cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, kernel-team@fb.com, pjt@google.com, luto@amacapital.net, efault@gmx.de, torvalds@linux-foundation.org, Roman Gushchin References: <1521649309-26690-1-git-send-email-longman@redhat.com> <1521649309-26690-3-git-send-email-longman@redhat.com> <20180322084120.GE7231@localhost.localdomain> <20180323075952.GA4763@localhost.localdomain> <20180326124711.GE5942@localhost.localdomain> <20180327140259.GN1840639@devbig577.frc2.facebook.com> From: Waiman Long Organization: Red Hat Message-ID: Date: Tue, 27 Mar 2018 10:23:33 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: <20180327140259.GN1840639@devbig577.frc2.facebook.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/27/2018 10:02 AM, Tejun Heo wrote: > Hello, > > On Mon, Mar 26, 2018 at 04:28:49PM -0400, Waiman Long wrote: >> Maybe we can have a different root level flag, say, >> sched_partition_domain that is equivalent to !sched_load_balnace. >> However, I am still not sure if we should enforce that no task should be >> in the root cgroup when the flag is set. >> >> Tejun and Peter, what are your thoughts on this? > I haven't looked into the other issues too much but we for sure cannot > empty the root cgroup. > > Thanks. > Now, I have a different idea. How about we add a special root-only knob, say, "cpuset.cpus.isolated" that contains the list of CPUs that are still owned by root, but not participated in load balancing. All the tasks in the root are load-balanced among the remaining CPUs. A child can then be created that hold some or all the CPUs in the isolated set. It will then have a separate root domain if load balancing is on, or an isolated cpuset if load balancing is off. Will that idea work? Cheers, Longman