Linux-rt-users archive on
 help / color / Atom feed
From: Elana Copperman <>
To: linux-rt-users <>,
	Steven Rostedt <>,
	Thomas Gleixner <>
Cc: "Vladimir Kondratiev (Mobileye)" 
Subject: Re: cgroups CPU time management + PREEMPT_RT
Date: Tue, 12 May 2020 13:30:27 +0000
Message-ID: <> (raw)
In-Reply-To: <>

Hi, can you help to clarify if there is any implementation support or evidence on configuring cgroups CPU time allocations for RT tasks in conjunction with the PREEMPT_RT patch?

Or are the two requirements contradictory in essence and not jointly feasible?


Elana and Vladimir

From: Elana Copperman

Sent: Thursday, May 7, 2020 10:08 PM

To: linux-rt-users <>; Vladimir Kondratiev (Mobileye) <>

Subject: RE: cgroups CPU time management + PREEMPT_RT



We are new to the mailing list, and new to PREEMPT_RT.

We are working on a project with a safety requirement to configure cgroups for resource management, as well as functional requirement for deployment of PREEMPT_RT patch.

cgroups in general can be used in this context, in particular for managing resources such as memory; and even for managing CPU time for non-RT tasks. 

However, we do see a potential problem with RT tasks, and how the CPU controller would work with the RT scheduling.

There is some obvious concern here, and this seems to be backed by what I find online regarding this question.

Can you help us to clarify what is the current state of implementation, and if there is any support for cgroup CPU controller configuration to work effectively with PREEMPT_RT for RT tasks? 



  parent reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2020-05-07 19:08 ` Elana Copperman
     [not found]   ` <>
2020-05-12 13:30     ` Elana Copperman [this message]
2020-05-12 13:36       ` Steven Rostedt
2020-05-12 13:41         ` Elana Copperman
2020-05-26 14:33           ` Sebastian Andrzej Siewior
     [not found]             ` <>
2020-05-26 15:01               ` Elana Copperman

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:

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

  git send-email \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-rt-users archive on

Archives are clonable:
	git clone --mirror linux-rt-users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-rt-users linux-rt-users/ \
	public-inbox-index linux-rt-users

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone