Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp656244iog; Mon, 13 Jun 2022 10:00:19 -0700 (PDT) X-Google-Smtp-Source: AGRyM1t5OrrGYBJOtk5Ke7nC6LACv/5JOVZJrzsf/wOHUcsKkp1HMjnMIbg0KUvvN8fJuMapjRBH X-Received: by 2002:a17:90b:4a4c:b0:1e4:da3a:9b07 with SMTP id lb12-20020a17090b4a4c00b001e4da3a9b07mr759149pjb.242.1655139618863; Mon, 13 Jun 2022 10:00:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1655139618; cv=none; d=google.com; s=arc-20160816; b=vDIfYJGsoui/WL41jaMOEv1w5u/5/12+63TdJCWa2NKRfCkPX94WLVdhT0rjr7ZMP/ CiZGp5Q7byu6MJbH95OBE3eBw1GLpLE7bv8xwo8NFgVN2faKSiRdi+5/06JYsEFQR6vS cvB6tf3BE9LGcy9g47NfKBAx0jBaGw6FjIsHTtyvZkr+t40/I7nsDf2uF9N0sKbRGweo 4CKb8G8ORgLN++WZMOQOZW7tDEriWv46JLfl9FSuML/VPRiurJEXLIXc9vK2yCAm+Qcf q9coaUUpUJlFbSRQKSKHX4WOyI+tp+l3gV6isoAWtVmV0qMFhfwFks/Oe3JXAkqizyvP p4qg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=f5Lm2wWyGosZM6z8k7SEF9qOMpYtGM8nzWGhua6hIYw=; b=bwosADSweKSbzDG5QyXsRqpsvrk/saEkXLAkv8wVyYvLOmr3OdR7YHCeBtqMcywN6w L0VjJ3rxoOrG2B8G7isP6RQdvj0b3uQJNiZD9OQhoNHYLdwjF9ui/H0L9OpBOj6Tr+q+ wM2Sta3JuKzxgcLSlc9svbhb0kP+WWdvJDP5vmGo5s7FLgatjeFtO+7j6A8QA2xYuUz4 Nnvw1MxyMymTlqdt/yycA/QiCmEowkZJXwnx21slYgb+AKmlblc3KM9R7jfwdrfhf0ac hL+sahYLsLBc/iGpfxgeLj72M9dByJuVonOZ9lMSjQwqk0xN0OUhgQi0rxnEuqxxw062 is8Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="aQxCYw6/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id np7-20020a17090b4c4700b001e6f83a6998si17182770pjb.56.2022.06.13.10.00.05; Mon, 13 Jun 2022 10:00:18 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="aQxCYw6/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244176AbiFMPou (ORCPT + 99 others); Mon, 13 Jun 2022 11:44:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59248 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1351258AbiFMPoM (ORCPT ); Mon, 13 Jun 2022 11:44:12 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id F27AAE84 for ; Mon, 13 Jun 2022 06:19:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1655126346; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=f5Lm2wWyGosZM6z8k7SEF9qOMpYtGM8nzWGhua6hIYw=; b=aQxCYw6/0qtiepuqjaiGzkIVo00LZiNleFV24Qojp6Wud5YmGbSFxjGrd6f/QbuL4Vna9t x+o7MDJCdLIajaXtf4+zYHd3Zw4Ey4SBtxSmBX/mGojjiILgZ8SswDob8UYA3DoGhPLHHv 3aughk/Hi/Fk/g9sJBBANkj6Z62KSwg= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-569--wfr7ystMWKUEgkXXr7izQ-1; Mon, 13 Jun 2022 09:19:04 -0400 X-MC-Unique: -wfr7ystMWKUEgkXXr7izQ-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id B9B8B28224F2; Mon, 13 Jun 2022 13:18:56 +0000 (UTC) Received: from [10.18.17.215] (dhcp-17-215.bos.redhat.com [10.18.17.215]) by smtp.corp.redhat.com (Postfix) with ESMTP id 0BF2F2026D64; Mon, 13 Jun 2022 13:18:56 +0000 (UTC) Message-ID: <8d7ddb5a-0d0b-3f2e-e049-900360e95fc6@redhat.com> Date: Mon, 13 Jun 2022 09:18:55 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: [PATCH v11 7/8] cgroup/cpuset: Update description of cpuset.cpus.partition in cgroup-v2.rst Content-Language: en-US To: Tejun Heo Cc: Zefan Li , Johannes Weiner , Jonathan Corbet , Shuah Khan , cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org, Andrew Morton , Roman Gushchin , Phil Auld , Peter Zijlstra , Juri Lelli , Frederic Weisbecker , Marcelo Tosatti , =?UTF-8?Q?Michal_Koutn=c3=bd?= References: <20220510153413.400020-1-longman@redhat.com> <20220510153413.400020-8-longman@redhat.com> <404171dc-0da3-21f2-5003-9718f875e967@redhat.com> From: Waiman Long In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.78 on 10.11.54.4 X-Spam-Status: No, score=-4.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 6/12/22 23:12, Tejun Heo wrote: > Hello, > > On Sun, Jun 12, 2022 at 11:02:38PM -0400, Waiman Long wrote: >> That is the behavior enforced by setting the CPU_EXCLUSIVE bit in cgroup v1. >> I haven't explicitly change it to make it different in cgroup v2. The major >> reason is that I don't want change to one cpuset to affect a sibling >> partition as it may make the code more complicate to validate if a partition >> is valid. > If at all possible, I'd really like to avoid situations where a parent can't > withdraw resources due to something that a descendant does. No, it doesn't affect parent at all. It just limit whats the siblings can do due to their mutual constraint. If this is what the confusion is about, I will try to reword the doc text. Cheers, Longman