mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shashank Balaji via B4 Relay <devnull+shashank.mahadasyam.sony.com@kernel.org>
To: "Tejun Heo" <tj@kernel.org>,
	"Johannes Weiner" <hannes@cmpxchg.org>,
	"Michal Koutný" <mkoutny@suse.com>,
	"Jonathan Corbet" <corbet@lwn.net>
Cc: 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>,
	 Shashank Balaji <shashank.mahadasyam@sony.com>
Subject: [PATCH 0/2] cgroup, docs: Clarify interaction of RT processes with cgroup v2 cpu controller
Date: Wed, 05 Mar 2025 13:12:42 +0900	[thread overview]
Message-ID: <20250305-rt-and-cpu-controller-doc-v1-0-7b6a6f5ff43d@sony.com> (raw)

Currently, CONFIG_RT_GROUP_SCHED is practically unusable. If enabled,
the cpu controller can be enabled only when all the realtime processes are in
the root cgroup. This has been clarified by Waiman Long in commit
20d4628 (cgroup, docs: Clarify limitation of RT processes with cgroup v2
cpu controller): https://lore.kernel.org/lkml/20240320142302.1790171-1-longman@redhat.com/

But this limitation does not affect any of the other controllers:
irrespective of CONFIG_RT_GROUP_SCHED, the other controllers can be used
for the resource control of realtime processes. This is made more
explicit in the first patch.

Even when CONFIG_RT_GROUP_SCHED is disabled, the runtime of realtime
processes is accounted for by cpu.pressure, and the usage_usec, user_usec,
and system_usec fields of cpu.stat, and cpu.uclamp.{min, max} affect
realtime processes as well. This is documented in the second patch.

Signed-off-by: Shashank Balaji <shashank.mahadasyam@sony.com>
---
Shashank Balaji (2):
      cgroup, docs: Be explicit about independence of RT_GROUP_SCHED and non-cpu controllers
      cgroup, docs: Document interaction of RT processes with cpu controller

 Documentation/admin-guide/cgroup-v2.rst | 41 ++++++++++++++++++++++-----------
 1 file changed, 27 insertions(+), 14 deletions(-)
---
base-commit: 9b381a28f44a49b92b03bb3982728f9cb67ee225
change-id: 20250226-rt-and-cpu-controller-doc-8a8aac572f3e

Best regards,
-- 
Shashank Balaji <shashank.mahadasyam@sony.com>



             reply	other threads:[~2025-03-05  4:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05  4:12 Shashank Balaji via B4 Relay [this message]
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
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=20250305-rt-and-cpu-controller-doc-v1-0-7b6a6f5ff43d@sony.com \
    --to=devnull+shashank.mahadasyam.sony.com@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 \
    --cc=tj@kernel.org \
    /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®