From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18])
	(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 A7B03361668
	for <linux-kernel@vger.kernel.org>; Wed, 27 May 2026 19:04:38 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18
ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116;
	t=1779908679; cv=none; b=aqNNjhiRY7mwILvvGu/ILl9VmMjGSmxDLPRyGRtWB5Gz6jIeZucwXACyDy15s+4djNkTOrAjadiwp4lPS3zmNH44fHqO3lATDuF+PjXd1y0u0vqCRK9hFWIsuRXSoPBQ2G2HyUzLWFWVVGrG1QfH7lHFeGehSBH1HcscPpe3I3Y=
ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org;
	s=arc-20240116; t=1779908679; c=relaxed/simple;
	bh=HdrsBa7sdbCzUC5njuWQLNij/n1S91EjLXCaGG0ooqU=;
	h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:
	 Content-Type:Content-Disposition:In-Reply-To; b=PENBxpjv/X3mgN6wGLtAd/ugXLywX03WCLSL1SuVEAXffjB0meGpEK1X1WRs2CYMdsx3zct2O5162V4WqGFDj6knIuaqMKDe/4ivjPNVEfkSpfaocp40tJm0UB9D6f5oyZeEzf+TFlM47jc5DDQ0KS7TLHlkCgCS5sftfaIMGNU=
ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=GCmMMV9J; arc=none smtp.client-ip=100.103.45.18
Authentication-Results: smtp.subspace.kernel.org;
	dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="GCmMMV9J"
Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3086E1F000E9;
	Wed, 27 May 2026 19:04:38 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org;
	s=k20260515; t=1779908678;
	bh=vL/mmN23hwmlkmF/bmgWbIfVxvZz4Eqpg+d8F0k4LbE=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To;
	b=GCmMMV9JfE+Ila45U9T3Wt8ggbJzUAw9oAkzgy2om+2vSzWq4qCWCoiAHUcRJlXRW
	 mLfM04j3HX+0NAc9jvJCkG57yl7L9/VvYWwnvjEtRtiFtVNNGb1n/Ud39L3xhPTVLp
	 JVPLJY/aKfMfAi4MMJZyzRT0Hv+BkO27z1DEp4EVqPkwQu4IqR44aXjjtHMW2BFx01
	 3lKgeEyRqM3KPF4UuUlfO93cSn/RZAHH2nsDbEfdQEowrTLqjRmhJgSOiazUGBkczQ
	 Rk+K7hv1Ho6QbU/9UatheMeG55BxMziR1oC2kqueNSfWLxiUuf53iAS+ImtNHTWLzv
	 WSqmYmgkfNmwg==
Date: Wed, 27 May 2026 09:04:37 -1000
From: Tejun Heo <tj@kernel.org>
To: Fernand Sieber <sieberf@amazon.com>
Cc: Ingo Molnar <mingo@redhat.com>, Peter Zijlstra <peterz@infradead.org>,
	Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	David Vernet <void@manifault.com>, Andrea Righi <arighi@nvidia.com>,
	Changwoo Min <changwoo@igalia.com>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	linux-kernel@vger.kernel.org, nh-open-source@amazon.com,
	Fahad Mubeen <fmubeen@amazon.de>,
	Hendrik Borghorst <hborghor@amazon.de>,
	David Woodhouse <dwmw@amazon.co.uk>
Subject: Re: [PATCH 1/2] sched/fair: expose cpu.max.runtime to set bandwidth
 runtime directly
Message-ID: <ahdARaXc-glZcTW4@slm.duckdns.org>
References: <20260525193622.70282-1-sieberf@amazon.com>
 <20260525193622.70282-2-sieberf@amazon.com>
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
List-Id: <linux-kernel.vger.kernel.org>
List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20260525193622.70282-2-sieberf@amazon.com>

On Mon, May 25, 2026 at 09:36:21PM +0200, Fernand Sieber wrote:
> Add a cpu.max.runtime cgroup v2 interface that allows userspace to set
> the CFS bandwidth controller's runtime directly. This enables CPU credit
> injection: an orchestrator writes a runtime budget which the cgroup
> consumes naturally through the existing bandwidth enforcement mechanism.

Can you detail the use case? What problem is it solving how?

Thanks.

-- 
tejun