linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shashank Balaji <shashank.mahadasyam@sony.com>
To: Tejun Heo <tj@kernel.org>
Cc: "Johannes Weiner" <hannes@cmpxchg.org>,
	"Michal Koutný" <mkoutny@suse.com>,
	"Jonathan Corbet" <corbet@lwn.net>,
	cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Shinya Takumi" <shinya.takumi@sony.com>,
	shashank.mahadasyam@sony.com
Subject: Re: [PATCH v2 3/3] cgroup, docs: cpu controller interaction with various scheduling policies
Date: Wed, 21 May 2025 16:49:43 +0900	[thread overview]
Message-ID: <aC2Fl4DVRbn6bS8H@JPC00244420> (raw)
In-Reply-To: <aCzjJp1ovS6kCqHj@slm.duckdns.org>

Hi Tejun,

On Tue, May 20, 2025 at 10:16:38AM -1000, Tejun Heo wrote:
> Hello,
> 
> On Tue, May 20, 2025 at 11:07:47PM +0900, Shashank Balaji via B4 Relay wrote:
> ...
> > +The interaction of a process with the cpu controller depends on its scheduling
> > +policy. We have the following scheduling policies: ``SCHED_IDLE``, ``SCHED_BATCH``,
> > +``SCHED_OTHER``, ``SCHED_EXT`` (if ``CONFIG_SCHED_CLASS_EXT`` is enabled), ``SCHED_FIFO``,
> > +``SCHED_RR``, and ``SCHED_DEADLINE``. ``SCHED_{IDLE,BATCH,OTHER,EXT}`` can be scheduled
> > +either by the fair-class scheduler or by a BPF scheduler::
> > +
> > +    CONFIG_SCHED_CLASS_EXT
> > +    ├─ Disabled
> > +    |   └─ SCHED_{IDLE,BATCH,OTHER} -> fair-class scheduler
> > +    └─ Enabled
> > +        ├─ BPF scheduler disabled
> > +        |   └─ SCHED_{IDLE,BATCH,OTHER,EXT} -> fair-class scheduler
> > +        ├─ BPF scheduler without SCX_OPS_SWITCH_PARTIAL enabled
> > +        |   └─ SCHED_{IDLE,BATCH,OTHER,EXT} -> BPF scheduler
> > +        └─ BPF scheduler with SCX_OPS_SWITCH_PARTIAL enabled
> > +            ├─ SCHED_{IDLE,BATCH,OTHER} -> fair-class scheduler
> > +            └─ SCHED_EXT -> BPF scheduler
> > +
> > +For more details on ``SCHED_EXT``, check out :ref:`Documentation/scheduler/sched-ext.rst. <sched-ext>`
> > +From the point of view of the cpu controller, processes can be categorized as
> > +follows:
> > +
> > +* Processes under the fair-class scheduler
> > +* Processes under a BPF scheduler with the ``cgroup_set_weight`` callback
> > +* Everything else: ``SCHED_{FIFO,RR,DEADLINE}`` and processes under a BPF scheduler
> > +  without the ``cgroup_set_weight`` callback
> > +
> > +Note that the ``cgroup_*`` family of callbacks require ``CONFIG_EXT_GROUP_SCHED``
> > +to be enabled. For each of the following interface files, the above categories
> > +will be referred to. All time durations are in microseconds.
> 
> Can we document the above in sched_ext documentation and point to it from
> here? Documenting sched_ext details here seems a bit out of place and prone
> to becoming stale over time.

Got it. Apart from that, is the content alright? 

> Can you please separate out indentation changes to a separate patch? These
> usually make reviewing tricky.

Got it.

Thank you

Regards,
Shashank

PS: Apologies for any malformed emails. I finally managed to switch from Outlook
to mutt.

  reply	other threads:[~2025-05-21  8:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-20 14:07 [PATCH v2 0/3] cgroup, docs: cpu controller interaction with various scheduling policies Shashank Balaji via B4 Relay
2025-05-20 14:07 ` [PATCH v2 1/3] cgroup, docs: be specific about bandwidth control of rt processes Shashank Balaji via B4 Relay
2025-05-20 20:11   ` Tejun Heo
2025-05-21  1:14     ` Shashank.Mahadasyam
2025-05-21 16:30       ` Tejun Heo
2025-05-21 16:35   ` Tejun Heo
2025-05-20 14:07 ` [PATCH v2 2/3] sched_ext, docs: add label Shashank Balaji via B4 Relay
2025-05-20 20:26   ` Tejun Heo
2025-05-20 14:07 ` [PATCH v2 3/3] cgroup, docs: cpu controller interaction with various scheduling policies Shashank Balaji via B4 Relay
2025-05-20 20:16   ` Tejun Heo
2025-05-21  7:49     ` Shashank Balaji [this message]
2025-05-21 17:31       ` Tejun Heo

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=aC2Fl4DVRbn6bS8H@JPC00244420 \
    --to=shashank.mahadasyam@sony.com \
    --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=mkoutny@suse.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;
as well as URLs for NNTP newsgroup(s).