From: Ingo Molnar <mingo@kernel.org>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
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>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, ltp@lists.linux.it
Subject: Re: [PATCH v2 2/2] docs: scheduler-rt: Clarify & fix sched_rt_* sysctl docs
Date: Thu, 28 Sep 2023 11:18:54 +0200 [thread overview]
Message-ID: <ZRVE/nQlVi1woRPf@gmail.com> (raw)
In-Reply-To: <20230927103012.9587-3-chrubis@suse.cz>
* Cyril Hrubis <chrubis@suse.cz> wrote:
> - Describe explicitly that sched_rt_runtime_us is allocated from
> sched_rt_period_us and hence always less or equal to that value.
Just some spelling nits:
> - The limit for sched_rt_runtime_us is not INT_MAX - 1 but rather it's
> limited by the value of sched_rt_period_us. If sched_rt_period_us is
> INT_MAX then sched_rt_runtime_us can be set to INT_MAX as well.
s/is not INT_MAX - 1 but rather it's
/is not INT_MAX-1, but rather it's
> /proc/sys/kernel/sched_rt_runtime_us:
> - A global limit on how much time realtime scheduling may use. Even without
> - CONFIG_RT_GROUP_SCHED enabled, this will limit time reserved to realtime
> - processes. With CONFIG_RT_GROUP_SCHED it signifies the total bandwidth
> - available to all realtime groups.
> + A global limit on how much time realtime scheduling may use. This is always
s/realtime
/real-time
> + less or equal than the period_us as it denotes the time allocated from the
s/than the period_us as it denotes
/than the period_us, as it denotes
> + period_us for the realtime tasks. Even without CONFIG_RT_GROUP_SCHED enabled,
> + this will limit time reserved to realtime processes. With
s/realtime
/real-time
> + CONFIG_RT_GROUP_SCHED it signifies the total bandwidth available to all
s/CONFIG_RT_GROUP_SCHED
/CONFIG_RT_GROUP_SCHED=y
> + realtime groups.
s/realtime
/real-time
Thanks,
Ingo
prev parent reply other threads:[~2023-09-28 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 10:30 [PATCH v2 0/2] Fix sched-rt sysctl files & update docs Cyril Hrubis
2023-09-27 10:30 ` [PATCH v2 1/2] sched/rt: Disallow writing invalid values to sched_rt_period_us Cyril Hrubis
2023-09-27 10:30 ` [PATCH v2 2/2] docs: scheduler-rt: Clarify & fix sched_rt_* sysctl docs Cyril Hrubis
2023-09-28 9:18 ` Ingo Molnar [this message]
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=ZRVE/nQlVi1woRPf@gmail.com \
--to=mingo@kernel.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=chrubis@suse.cz \
--cc=corbet@lwn.net \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
/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).