From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C66C347AF57; Mon, 11 May 2026 18:15:18 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778523318; cv=none; b=cocbvvWFQKQyLjzbtM5WoMeSGSSb+EHGPQY9GiWz3uJEKeNKXBHO3GidwKP7XUDXvdmoEtd9dmfVCNg28UxxP4ikLBi5BYdogMwq8kfZ2kGZC7WdEPtvrJc86bOvqxtJd3yk/5NNMFtMD6jUjB29/7WgJVxP+bnfJtTDxPZ3oA8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778523318; c=relaxed/simple; bh=alef+4cDl9DUVytr7Ik0sUxOdVcXNDM2M978SNtXdaw=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=aA8X198dVlkx21a10ttIhNgUR7YPSJU9sUQX+b0UDdB3Hmf7Sfl7N6oV3yM6xuDZx9+GZF29oMrQvr/Kgi8xOKHR8zbpZofWmquEl3E77JXora04xitTA+jThOT1+OAe4jtIzdqs/HVAvMZ7eQpZ9+JuBPymg7NOgVpo2EFXMT8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=S2uLs3iJ; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="S2uLs3iJ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 56522C2BCB0; Mon, 11 May 2026 18:15:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1778523318; bh=alef+4cDl9DUVytr7Ik0sUxOdVcXNDM2M978SNtXdaw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=S2uLs3iJih9nf3IJxqQvR2BXhg+GLm2e89Z4D0JYyFa7K2cHFHjriI9J054H88nvE KvZtg7R+krTXWhe+mIAjPWfmB1k89OTGvf3ebjHxbj9/Bg/isbd54rxxtBe5Z+CNf3 Jf+LcCegfXypsKiZk+N4M8E6s2/UYQPpop4QwO5Bh3dvYAuAGLIh4GZnVi//1DKsfs 0MjMM0kQ/uk8nOz8+yW4C1bNoBXr9ciO45NwbcsTI55QMBVZkKECgoCak3LTpwyuIH aEItcdrx/Vos+m1yZiObSD1RZLctwvAXGvy5HGLfAMNg9MU+5p2R97P7s3wUpdY5jj ZyWyTEVRzmSYA== Date: Mon, 11 May 2026 08:15:17 -1000 From: Tejun Heo To: luca abeni Cc: Peter Zijlstra , Yuri Andriaccio , Ingo Molnar , Juri Lelli , Vincent Guittot , Dietmar Eggemann , Steven Rostedt , Ben Segall , Mel Gorman , Valentin Schneider , linux-kernel@vger.kernel.org, Yuri Andriaccio , hannes@cmpxchg.org, mkoutny@suse.com, cgroups@vger.kernel.org Subject: Re: [RFC PATCH v5 20/29] sched/deadline: Allow deeper hierarchies of RT cgroups Message-ID: References: <20260430213835.62217-1-yurand2000@gmail.com> <20260430213835.62217-21-yurand2000@gmail.com> <20260505151523.GF3102624@noisy.programming.kicks-ass.net> <20260507105331.GQ1026330@noisy.programming.kicks-ass.net> <20260511114004.0fd8d54c@luca64> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260511114004.0fd8d54c@luca64> On Mon, May 11, 2026 at 11:40:04AM +0200, luca abeni wrote: > We are discussing this issue with Yuri, and we have a doubt: if we > disable the RT-CPU controller for a cgroup, would it be possible to > enable it for its children? > (In other words: if we want the RT-CPU controller to be enabled for > some "leaf" cgroups, we need to enable it for their parents, right?) Yeah, a cgroup has a controller available to it iff its parent enables that controller, so all ancestors would have to enable it. Thanks. -- tejun