From: Juri Lelli <juri.lelli@redhat.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: "Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
rcu@vger.kernel.org, linux-doc@vger.kernel.org,
"John Ogness" <john.ogness@linutronix.de>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Vincent Guittot" <vincent.guittot@linaro.org>,
"Dietmar Eggemann" <dietmar.eggemann@arm.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Ben Segall" <bsegall@google.com>, "Mel Gorman" <mgorman@suse.de>,
"Valentin Schneider" <vschneid@redhat.com>,
"K Prateek Nayak" <kprateek.nayak@amd.com>,
"luca abeni" <luca.abeni@santannapisa.it>,
"Yuri Andriaccio" <yurand2000@gmail.com>,
"Yuri Andriaccio" <yuri.andriaccio@santannapisa.it>,
"Frederic Weisbecker" <frederic@kernel.org>,
"Neeraj Upadhyay" <neeraj.upadhyay@kernel.org>,
"Joel Fernandes" <joelagnelf@nvidia.com>,
"Josh Triplett" <josh@joshtriplett.org>,
"Boqun Feng" <boqun@kernel.org>,
"Uladzislau Rezki" <urezki@gmail.com>,
"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
"Lai Jiangshan" <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang@linux.dev>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"Tejun Heo" <tj@kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Qais Yousef" <qyousef@layalina.io>
Subject: Re: [PATCH v2 0/7] sched: RT throttling cleanup and a bit of documentation
Date: Thu, 12 Nov 2026 16:01:06 +0100 [thread overview]
Message-ID: <avXUstjABxdTZaxM@jlelli-thinkpadt14gen4.remote.csb> (raw)
In-Reply-To: <c2bf89ce-b9de-43cf-839b-395d28b2275c@paulmck-laptop>
Hello,
On 10/11/26 11:56, Paul E. McKenney wrote:
> On Tue, Nov 10, 2026 at 06:34:42PM +0100, Sebastian Andrzej Siewior wrote:
> > People used to disable the RT throttling mechanism by writing -1 to
> > /proc/sys/kernel/sched_rt_runtime_us. Since v6.12 they can still do this
> > but they don't disable RT throttling anymore. Instead this throttling
> > mechanism has been taken over by the fair_server which can be configured
> > via debugfs.
> > This is not really documented by a hint appeared a few cycles later in
> > Documentation/scheduler/sched-rt-group.rst. This can be found once you
> > know what you are looking for because this document describes the RT
> > group scheduling (CONFIG_RT_GROUP_SCHED). The fair_server is used even
> > without it.
> > The then there is global DL resource control which also shares this
> > file proc file (which is stuck if CONFIG_RT_GROUP_SCHED is enabled).
>
> Nice, thank you!
>
> Unfortunately but unsurprisingly, this gets the same divide-by-zero
> issue reported (belatedly) on the earlier series:
>
> https://lore.kernel.org/all/e58e48c3-ac62-40cd-b5d3-2de87db12496@paulmck-laptop/
>
I wonder if this fixes is
https://lore.kernel.org/lkml/20261108185406.1549770-6-mathieu.desnoyers@efficios.com/
Thanks,
Juri
next prev parent reply other threads:[~2026-11-12 15:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 17:34 Sebastian Andrzej Siewior
2026-11-10 17:34 ` [PATCH v2 1/7] sched: Mark RT_GROUP_SCHED broken Sebastian Andrzej Siewior
2026-11-10 17:42 ` Randy Dunlap
2026-11-11 13:37 ` Sebastian Andrzej Siewior
2026-11-11 16:54 ` Randy Dunlap
2026-11-10 17:34 ` [PATCH v2 2/7] rcutorture: Don't try to disable to RT throttling Sebastian Andrzej Siewior
2026-11-10 17:34 ` [PATCH v2 3/7] sched: rcutorture: Allow to disable DL fair_server Sebastian Andrzej Siewior
2026-11-10 17:34 ` [PATCH v2 4/7] sched: Move DL's admission control to sysfs Sebastian Andrzej Siewior
2026-11-10 17:34 ` [PATCH v2 5/7] sched: Limit sysctl sched_rt_{period|runtime}_us to RT_GROUP_SCHED Sebastian Andrzej Siewior
2026-11-10 17:34 ` [PATCH v2 6/7] sched: Add sysfs files for the per-CPU fair_server knobs Sebastian Andrzej Siewior
2026-11-10 17:34 ` [PATCH v2 7/7] Documentation/sched: Add fairserver to sched-deadline Sebastian Andrzej Siewior
2026-11-10 19:56 ` [PATCH v2 0/7] sched: RT throttling cleanup and a bit of documentation Paul E. McKenney
2026-11-12 15:01 ` Juri Lelli [this message]
2026-11-12 15:24 ` Sebastian Andrzej Siewior
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=avXUstjABxdTZaxM@jlelli-thinkpadt14gen4.remote.csb \
--to=juri.lelli@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=boqun@kernel.org \
--cc=bsegall@google.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=dave@stgolabs.net \
--cc=dietmar.eggemann@arm.com \
--cc=frederic@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=jiangshanlai@gmail.com \
--cc=joelagnelf@nvidia.com \
--cc=john.ogness@linutronix.de \
--cc=josh@joshtriplett.org \
--cc=kprateek.nayak@amd.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@santannapisa.it \
--cc=mathieu.desnoyers@efficios.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=mkoutny@suse.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=qiang.zhang@linux.dev \
--cc=qyousef@layalina.io \
--cc=rcu@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.org \
--cc=tj@kernel.org \
--cc=urezki@gmail.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=yurand2000@gmail.com \
--cc=yuri.andriaccio@santannapisa.it \
/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®