mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: shashank.mahadasyam@sony.com
Cc: "Johannes Weiner" <hannes@cmpxchg.org>,
	"Michal Koutný" <mkoutny@suse.com>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Waiman Long" <longman@redhat.com>,
	cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Shinya Takumi" <shinya.takumi@sony.com>
Subject: Re: [PATCH 1/2] cgroup, docs: Be explicit about independence of RT_GROUP_SCHED and non-cpu controllers
Date: Wed, 5 Mar 2025 08:44:45 -1000	[thread overview]
Message-ID: <Z8ibndhPN10cL9Gs@slm.duckdns.org> (raw)
In-Reply-To: <20250305-rt-and-cpu-controller-doc-v1-1-7b6a6f5ff43d@sony.com>

On Wed, Mar 05, 2025 at 01:12:43PM +0900, Shashank Balaji via B4 Relay wrote:
> From: Shashank Balaji <shashank.mahadasyam@sony.com>
> 
> The cgroup v2 cpu controller has a limitation that if
> CONFIG_RT_GROUP_SCHED is enabled, the cpu controller can be enabled only
> if all the realtime processes are in the root cgroup. The other
> controllers have no such restriction. They can be used for the resource
> control of realtime processes irrespective of whether
> CONFIG_RT_GROUP_SCHED is enabled or not.
> 
> Signed-off-by: Shashank Balaji <shashank.mahadasyam@sony.com>

Applied to cgroup/for-6.15.

Thanks.

-- 
tejun

  parent reply	other threads:[~2025-03-05 18:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05  4:12 [PATCH 0/2] cgroup, docs: Clarify interaction of RT processes with cgroup v2 cpu controller Shashank Balaji via B4 Relay
2025-03-05  4:12 ` [PATCH 1/2] cgroup, docs: Be explicit about independence of RT_GROUP_SCHED and non-cpu controllers Shashank Balaji via B4 Relay
2025-03-05 14:13   ` Waiman Long
2025-03-05 16:15   ` Michal Koutný
2025-03-05 18:44   ` Tejun Heo [this message]
2025-03-05  4:12 ` [PATCH 2/2] cgroup, docs: Document interaction of RT processes with cpu controller Shashank Balaji via B4 Relay
2025-03-05 14:16   ` Waiman Long
2025-03-06 10:23     ` Shashank.Mahadasyam
2025-03-05 16:19   ` Michal Koutný
2025-03-06 11:02     ` Shashank.Mahadasyam
2025-03-10 17:14       ` Michal Koutný
2025-03-28 10:45         ` Shashank.Mahadasyam
2025-04-02 12:49           ` Michal Koutný

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Z8ibndhPN10cL9Gs@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=corbet@lwn.net \
    --cc=hannes@cmpxchg.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mkoutny@suse.com \
    --cc=shashank.mahadasyam@sony.com \
    --cc=shinya.takumi@sony.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®