Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7FA0CC433FE for ; Thu, 16 Dec 2021 09:28:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235405AbhLPJ2o (ORCPT ); Thu, 16 Dec 2021 04:28:44 -0500 Received: from smtp-out1.suse.de ([195.135.220.28]:60974 "EHLO smtp-out1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235360AbhLPJ2k (ORCPT ); Thu, 16 Dec 2021 04:28:40 -0500 Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id E869621135; Thu, 16 Dec 2021 09:28:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1639646918; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=fGxktS/Uc4QdkNKSXK/IVadOzTG1ebMs/QUmVV6nIcE=; b=Eh2Wx8s9jDwfC6jxKZuaZRo24mG2IrIk9796h9H2/iwEim4E06TJFI8j6yq9/wyc9rjpJo 396WeJCIzR7D9qq7Fr4tJgnwzwqPCQ6m9OgWHc/zxKAv52j9ARDUZxGkKQjCS636XLM66F Tp76ek5AjK/Gkf8uXf/sx+eEV3Povs0= Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id AABE813C1F; Thu, 16 Dec 2021 09:28:38 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id Y/wQKcYGu2FtYQAAMHmgww (envelope-from ); Thu, 16 Dec 2021 09:28:38 +0000 Date: Thu, 16 Dec 2021 10:28:37 +0100 From: Michal =?iso-8859-1?Q?Koutn=FD?= To: Waiman Long Cc: Tejun Heo , 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 Subject: Re: [PATCH v9 3/7] cgroup/cpuset: Refining features and constraints of a partition Message-ID: <20211216092837.GB46450@blackbody.suse.cz> References: <20211205183220.818872-1-longman@redhat.com> <20211205183220.818872-4-longman@redhat.com> <20211215144944.GE16798@blackbody.suse.cz> <98887e63-51de-f5ad-8fb8-56269aaf4bcf@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <98887e63-51de-f5ad-8fb8-56269aaf4bcf@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 15, 2021 at 11:29:41AM -0500, Waiman Long wrote: > There are additional checks for the member to partition transition which > requires that the target cpuset shouldn't have child cpuset. Ah, I forgot the transition condition no. 4 will apply here. Clear. So, currently full bottom up + top down walk is needed in (rare?) case the switch from root partition to member and back. > That prevents the recovering of a invalid partition root under a > member cpuset. We could certainly remove that restriction by adding > additional code as well as additional tests to verify it works. I > haven't done that simply to avoid adding more complexity to the > current code. I agree this restriction can be lifted later independently when the rest settles. (It's not so different from controllers disabling on the unified hierarchy after all.) Thanks, Michal