All of lore.kernel.org
 help / color / mirror / Atom feed
From: Elana Copperman <Elana.Copperman@mobileye.com>
To: linux-rt-users <linux-rt-users@vger.kernel.org>,
	"Vladimir Kondratiev (Mobileye)" 
	<63dc4b5d-c467-4bfb-bce5-74485907c850@intel.mail.onmicrosoft.com>
Subject: RE: cgroups CPU time management + PREEMPT_RT
Date: Thu, 7 May 2020 19:08:21 +0000	[thread overview]
Message-ID: <AM0PR09MB3794E9CFE8BA31852B712DAD99A50@AM0PR09MB3794.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <AM0PR09MB3794D873EEAE20CD9201D14299A50@AM0PR09MB3794.eurprd09.prod.outlook.com>

Hi,
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?  
Thanks 
Elana


       reply	other threads:[~2020-05-07 19:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AM0PR09MB3794D873EEAE20CD9201D14299A50@AM0PR09MB3794.eurprd09.prod.outlook.com>
2020-05-07 19:08 ` Elana Copperman [this message]
     [not found]   ` <AM0PR09MB3794F5E857CB761859BBEF0B99BE0@AM0PR09MB3794.eurprd09.prod.outlook.com>
2020-05-12 13:30     ` cgroups CPU time management + PREEMPT_RT Elana Copperman
2020-05-12 13:36       ` Steven Rostedt
2020-05-12 13:41         ` Elana Copperman
2020-05-26 14:33           ` Sebastian Andrzej Siewior
     [not found]             ` <AM0PR09MB37947DEF27E4D91EE8B0BD1A99B00@AM0PR09MB3794.eurprd09.prod.outlook.com>
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:
  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=AM0PR09MB3794E9CFE8BA31852B712DAD99A50@AM0PR09MB3794.eurprd09.prod.outlook.com \
    --to=elana.copperman@mobileye.com \
    --cc=63dc4b5d-c467-4bfb-bce5-74485907c850@intel.mail.onmicrosoft.com \
    --cc=linux-rt-users@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.