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 1C3ABECDFB8 for ; Fri, 20 Jul 2018 11:31:48 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id AD3D820661 for ; Fri, 20 Jul 2018 11:31:47 +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="XPla7+BE" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org AD3D820661 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 S1728409AbeGTMTe (ORCPT ); Fri, 20 Jul 2018 08:19:34 -0400 Received: from merlin.infradead.org ([205.233.59.134]:55606 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727410AbeGTMTe (ORCPT ); Fri, 20 Jul 2018 08:19:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=merlin.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=SXbZTz5Xm2/AOPZI50e723sEbsMKkKj7CD7XVXdiu7Y=; b=XPla7+BE3HaQKI4SF/MhWUa8g GzqJ5t7svGuTrMnUxJsU3iNbPpTbDzFuaIoJFCUZ8fH2p8H3fq37INwTkfBER9CXmXbBOdWcuxBW6 nJWSioSVHU3uXedtnP9FkfizI2+q02EVXfQLmlXWc+XmYKEATlhwDjK7kHyKP++T8L23gmQT0KRpp X8W/0IBkTD3T+SvBf/CNgl0wys4TSxLQCueBLEmmFBr2f4xUzd3RUTN2Glloo807FYSpshJ6sKTKE VyLaf8c+qPoBaIndVFL4vfQaM/1tsIQixhS/jJba7O6WxaCiqh74CHbAHuxJ0zHuRhq86Htj4mrCR E4XI6jUCA==; Received: from j217100.upc-j.chello.nl ([24.132.217.100] helo=hirez.programming.kicks-ass.net) by merlin.infradead.org with esmtpsa (Exim 4.90_1 #2 (Red Hat Linux)) id 1fgTd6-00027J-CJ; Fri, 20 Jul 2018 11:31:25 +0000 Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id A847D20275F47; Fri, 20 Jul 2018 13:31:21 +0200 (CEST) Date: Fri, 20 Jul 2018 13:31:21 +0200 From: Peter Zijlstra To: Tejun Heo Cc: Waiman Long , 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: <20180720113121.GJ2476@hirez.programming.kicks-ass.net> References: <1529825440-9574-1-git-send-email-longman@redhat.com> <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180719165201.GU72677@devbig577.frc2.facebook.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 09:52:01AM -0700, Tejun Heo wrote: > Hello, > > On Thu, Jul 19, 2018 at 11:52:46AM -0400, Waiman Long wrote: > > BTW, the way the partition is currently implemented right now is that a > > child cannot be a partition root unless its parent is a partition root > > itself. That is to avoid turning on partition to affect ancestors > > further up the hierarchy than just the parent. So in the case of a > > container, it cannot allocate sub-partitions underneath it unless it is > > a partition itself. Will that solve your concern? > > Hmm... so a given ancestor must be able to both > > 1. control which cpus are moved into a partition in all of its > subtree. By virtue of the partition file being owned by the parent, this is already achived, no? > 2. take away any given cpu from ist subtree. I really hate this obsession of yours and doubly so for partitions. But why would this currently not be allowed?