From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755443AbeDWOKm (ORCPT ); Mon, 23 Apr 2018 10:10:42 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:57580 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754962AbeDWOKl (ORCPT ); Mon, 23 Apr 2018 10:10:41 -0400 Subject: Re: [PATCH v7 0/5] cpuset: Enable cpuset controller in default hierarchy To: Juri Lelli Cc: Tejun Heo , 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, Mike Galbraith , torvalds@linux-foundation.org, Roman Gushchin References: <1524145624-23655-1-git-send-email-longman@redhat.com> <20180423130715.GA32341@localhost.localdomain> <20180423135756.GC32341@localhost.localdomain> From: Waiman Long Organization: Red Hat Message-ID: <22ad86e3-0661-6db0-f4f3-5b06f439dcf7@redhat.com> Date: Mon, 23 Apr 2018 10:10:39 -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: <20180423135756.GC32341@localhost.localdomain> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/23/2018 09:57 AM, Juri Lelli wrote: > On 23/04/18 15:07, Juri Lelli wrote: >> Hi Waiman, >> >> On 19/04/18 09:46, Waiman Long wrote: >>> v7: >>> - Add a root-only cpuset.cpus.isolated control file for CPU isolation. >>> - Enforce that load_balancing can only be turned off on cpusets with >>> CPUs from the isolated list. >>> - Update sched domain generation to allow cpusets with CPUs only >>> from the isolated CPU list to be in separate root domains. > Guess I'll be adding comments as soon as I stumble on something unclear > (to me :), hope that's OK (shout if I should do it differently). > > The below looked unexpected to me: > > root@debian-kvm:/sys/fs/cgroup# cat g1/cpuset.cpus > 2-3 > root@debian-kvm:/sys/fs/cgroup# cat g1/cpuset.mems > > root@debian-kvm:~# echo $$ > /sys/fs/cgroup/g1/cgroup.threads > root@debian-kvm:/sys/fs/cgroup# cat g1/cgroup.threads > 2312 > > So I can add tasks to groups with no mems? Or is it this only true in my > case with a single mem node? Or maybe it's inherited from root group > (slightly confusing IMHO if that's the case). No mems mean looking up the parents until we find one with non-empty mems. The mems.effective will show you the actual memory nodes used. -Longman