From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.1 required=3.0 tests=DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,T_DKIM_INVALID, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A72ECECDFB8 for ; Fri, 20 Jul 2018 11:32:30 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5DCBB20661 for ; Fri, 20 Jul 2018 11:32:30 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="iIA/PHJT" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 5DCBB20661 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730183AbeGTMUR (ORCPT ); Fri, 20 Jul 2018 08:20:17 -0400 Received: from bombadil.infradead.org ([198.137.202.133]:43458 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727410AbeGTMUR (ORCPT ); Fri, 20 Jul 2018 08:20:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=In-Reply-To:Content-Type:MIME-Version :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=LFKEgGNKGYlBzIjx7OFkg2ppIE+/ozpZvzoWPn6vY+c=; b=iIA/PHJTzRAIh4fdoabJgWFD1 jrNiqglElPUhxMTN1n7UJmZ2xlmhIEsMMPY3SjY/dCbeg9kxdGgt8iJSAuU4j5e3H43yxWlEretBt Jy71FRXqCjnnISPd+xEy7Sy8G9tYW0G3DyO/1TSLtOdHB/+Od/VhHx2299uV8YrmFEllwuwZHslPM Tqi6jCo1LCcO71U4OlOCpOAbrSkMPnsTeXHsx43u7cFoezgGBCXJeEh8nboMKUS96aS9gWFG8Mza9 tUUpmqm3jciUQJKbSMVMBjA+eDPTgids5PP5NoX3vese0Trq55ta6oaqST77HKiu0zu5Fd66I2WE8 HNwmwKcAw==; Received: from j217100.upc-j.chello.nl ([24.132.217.100] helo=hirez.programming.kicks-ass.net) by bombadil.infradead.org with esmtpsa (Exim 4.90_1 #2 (Red Hat Linux)) id 1fgTdz-0001PF-P6; Fri, 20 Jul 2018 11:32:19 +0000 Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id 4006220275F47; Fri, 20 Jul 2018 13:32:18 +0200 (CEST) Date: Fri, 20 Jul 2018 13:32:18 +0200 From: Peter Zijlstra To: Waiman Long Cc: Tejun Heo , Li Zefan , Johannes Weiner , 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 , Juri Lelli , Patrick Bellasi Subject: Re: [PATCH v11 7/9] cpuset: Expose cpus.effective and mems.effective on cgroup v2 root Message-ID: <20180720113218.GK2476@hirez.programming.kicks-ass.net> References: <1529825440-9574-8-git-send-email-longman@redhat.com> <20180702165322.GI533219@devbig577.frc2.facebook.com> <20180703155823.GS533219@devbig577.frc2.facebook.com> <20180719135224.GE2494@hirez.programming.kicks-ass.net> <1107494a-9667-df58-dcac-9366e969dc3a@redhat.com> <20180719153045.GT72677@devbig577.frc2.facebook.com> <20180719165201.GU72677@devbig577.frc2.facebook.com> <69903192-8711-6a1e-0cd0-fbb249a4204b@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <69903192-8711-6a1e-0cd0-fbb249a4204b@redhat.com> User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 19, 2018 at 01:22:36PM -0400, Waiman Long wrote: > > 1. control which cpus are moved into a partition in all of its > > subtree. > > Not at the moment. I do have another idea of adding a "cpus.subpart" > file, for example, to indicate what CPUs a child sub-partition can use > in its partition. ARGH, why more files; this is turning into a right mess to use.