public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Frederic Weisbecker <frederic@kernel.org>
Cc: linux-rt-users@vger.kernel.org, cgroups@vger.kernel.org
Subject: Re: Question Regarding isolcpus
Date: Thu, 12 Oct 2023 13:27:57 -0400	[thread overview]
Message-ID: <11efaeb8-eac1-4a12-8283-6e9ce168e809@canonical.com> (raw)
In-Reply-To: <20230928083909.KySJvo1d@linutronix.de>



On 9/28/23 04:39, Sebastian Andrzej Siewior wrote:
> On 2023-09-26 12:45:14 [-0400], Joseph Salisbury wrote:
>> Hi All,
> Hi,
>
>> I have a question regarding the isolcpus parameter.  I've been seeing this
>> parameter commonly used. However, in the kernel.org documentation[0],
>> isolcpus is listed as depreciated.
>>
>> Is it the case that isolcpus should not be used at all?  I've seen it used
>> in conjunction with taskset.  However, should we now be telling rt users to
>> use only cpusets in cgroups?  I see that CPUAffinity can be set in
>> /etc/systemd/system.conf.  Is that the preferred method, so the process
>> scheduler will automatically migrate processes between the cpusets in the
>> cgroup cpuset or the list set by CPUAffinity?
> Frederic might know if there is an actual timeline to remove it. The
> suggestions since then is to use cpusets which should be more flexible.
> There was also some work (which went into v6.1 I think) to be able to
> reconfigure the partitions at run-time while isolcpus= is a boot time
> option.
>  From what I remember, you have a default/system cpuset which all tasks
> use by default and then you can add another cpuset for the "isolated"
> CPUs. Based on the partition it can be either the default one or
> isolated [0]. The latter would exclude the CPUs from load balancing
> which is what isolcpus= does.
>
> [0] f28e22441f353 ("cgroup/cpuset: Add a new isolated cpus.partition type")

This question may be for the cgroups folks.  The kernel.org 
documentation has a WARNING which states: "cgroup2 doesn't yet support 
control of realtime processes and the cpu controller can only be enabled 
when all RT processes are in the root cgroup "[0]. Does this mean 
real-time processes are only supported on cgroupsV1?

Also, this warning is stated for the "CPU" Controller, but there is no 
mention of this for a "cpuset" controller. Does this imply that 
real-time processes are supported with "cpuset" controllers?


Thanks,

Joe

[0] 
https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html#controllers

>
>> Thanks,
>>
>> Joe
> Sebastian
>


  parent reply	other threads:[~2023-10-12 17:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26 16:45 Question Regarding isolcpus Joseph Salisbury
2023-09-28  8:39 ` Sebastian Andrzej Siewior
2023-09-28 19:19   ` Rod Webster
2023-09-28 21:03     ` Gautham
2023-10-12 17:27   ` Joseph Salisbury [this message]
2023-10-12 19:10     ` Waiman Long
2023-10-12 19:23       ` Joseph Salisbury
2023-10-13 18:07         ` Waiman Long

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=11efaeb8-eac1-4a12-8283-6e9ce168e809@canonical.com \
    --to=joseph.salisbury@canonical.com \
    --cc=bigeasy@linutronix.de \
    --cc=cgroups@vger.kernel.org \
    --cc=frederic@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox