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.4 required=3.0 tests=DKIM_SIGNED, 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 CBCFDECDFBB for ; Fri, 20 Jul 2018 17:41:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 76EA120652 for ; Fri, 20 Jul 2018 17:41:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="Pl5o/+18" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 76EA120652 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.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 S2388164AbeGTSaV (ORCPT ); Fri, 20 Jul 2018 14:30:21 -0400 Received: from mail-yw0-f196.google.com ([209.85.161.196]:37430 "EHLO mail-yw0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731305AbeGTSaV (ORCPT ); Fri, 20 Jul 2018 14:30:21 -0400 Received: by mail-yw0-f196.google.com with SMTP id w76-v6so4631198ywg.4; Fri, 20 Jul 2018 10:41:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=cwFuLmY72f0ORSsZ9OAumVPGmBV/AQlH7QKLVGd2oNA=; b=Pl5o/+18GRH9i/WZPjrEHnH3xfrmbYm7BON6a7jmSq5sF3+GRLSTqbeeqtYn+3iXLE IlYlR8zTN1r4vyBHxlYGZSNvFBykG51Bnj1Sn+O0+K8r86OBfJYnEOqVAdidxjwLaSF7 /O+pkY8WVMC+jLpTh/8Rlpb5/1cXey/xMa7tdqZkZdF4BBlFtBeVSxecbxl+N5vgsF0/ Sd7Wctlehg/wrpySRhUo8TFRdgFM77UjoUIN9/gCh/EC4fNpb1s7IBFC3B0Rfd3G8pV9 OPQ4D1rrhh1DsyY5Bp+fe1ZZzXLgBSUx4h/Ztm2QxNWIGbG8+lkxT70JSSJXJH+UvYWf sMvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=cwFuLmY72f0ORSsZ9OAumVPGmBV/AQlH7QKLVGd2oNA=; b=PNhsYo19rcTCOiJF3ftKr08PRnAEaRzk2ZtToeW4TN47PzBk+AjW7NDNmrk3uADdoF fOlHl8gPqyJjhkM97M5InJWD16vHwpQezxmZepOWav1GZwtur+0cj318kGi8kX+2L1y7 nKe7SXGI+Xnk1EXmeOCQHebPnpnbajEt1Z1lyc5Vk3t5DtEC75ViKBLz2b9StoD0hh0r s0rniSn+Q6qFz/KH6T06GdFXXt/WY9EVZXcbcmmxHVpvZvgRZyPN3/5R7DZiTmJ43iQd 3WewqgRsiXKv08Mbwv+kUBhdBqu+V9kwBfFYLz92LItfToqmF1yddahzsrXf4WONMOAV cBSA== X-Gm-Message-State: AOUpUlHRo0zXnplmOjUzaBLzoKoAuN5AciCbTU5lPGz6Q2RCRfc3xriN NkNNAoD5xuJ9mJr1MlXSezs= X-Google-Smtp-Source: AAOMgpd7HeKVK5z9xo3iYYL1DI1ScsG9/UjoUEIkcyEGmefRU3FJ/PPqhO54/eeO8dQRmM9nK7nzfA== X-Received: by 2002:a0d:ddc8:: with SMTP id g191-v6mr1549773ywe.145.1532108463068; Fri, 20 Jul 2018 10:41:03 -0700 (PDT) Received: from localhost ([2620:10d:c091:180::1:b56b]) by smtp.gmail.com with ESMTPSA id x69-v6sm2384166ywx.105.2018.07.20.10.41.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Jul 2018 10:41:02 -0700 (PDT) Date: Fri, 20 Jul 2018 10:41:00 -0700 From: Tejun Heo To: Waiman Long Cc: Peter Zijlstra , 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: <20180720174100.GC1934745@devbig577.frc2.facebook.com> References: <20180719153045.GT72677@devbig577.frc2.facebook.com> <20180719165201.GU72677@devbig577.frc2.facebook.com> <20180720113121.GJ2476@hirez.programming.kicks-ass.net> <20180720114549.GY72677@devbig577.frc2.facebook.com> <20180720154454.GR2494@hirez.programming.kicks-ass.net> <20180720155613.GB1934745@devbig577.frc2.facebook.com> <4857a9db-ebf5-24f8-c42d-d795f5c75854@redhat.com> <20180720163712.GU2494@hirez.programming.kicks-ass.net> <8c655adc-6d9e-b767-1024-5d6941c995a9@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8c655adc-6d9e-b767-1024-5d6941c995a9@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, On Fri, Jul 20, 2018 at 01:09:23PM -0400, Waiman Long wrote: > On 07/20/2018 12:37 PM, Peter Zijlstra wrote: > > On Fri, Jul 20, 2018 at 12:19:29PM -0400, Waiman Long wrote: > >> I am not against the idea of making it hierarchical eventually. I am > >> just hoping to get thing going by merging the patchset in its current > >> form and then we can make it hierarchical in a followup patch. > > Where's the rush? Why can't we do this right in one go? > > For me, the rush comes from RHEL8 as it is a goal to have a fully > functioning cgroup v2 in that release. > > I also believe that most of the use cases of partition can be satisfied > with partitions at the first level children. Getting hierarchical > partition right may drag on for half a year, maybe, giving our history > with cpu v2 controller. No matter what we do to enable hierarchical > partition in the future, the current model of using a partition flag is > intuitive enough that it won't be changed at least for the first level > children. I'm fully with Waiman here. There are people wanting to use it and the part most people isn't controversial at all. I don't see what'd be gained by further delaying the whole thing. If the first level partition thing isn't acceptable to everyone, we can even strip down further. We can get .cpus and .mems merged first, which is what most people want anyway. Thanks. -- tejun