From: Jonathan Corbet <corbet@lwn.net>
To: Zhang Qiao <zhangqiao22@huawei.com>
Cc: mingo@kernel.org, chrubis@suse.cz, zhangqiao22@huawei.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/Documentation: Add RT_RUNTIME_SHARE documentation
Date: Wed, 28 Feb 2024 15:44:14 -0700 [thread overview]
Message-ID: <875xy8p5tt.fsf@meer.lwn.net> (raw)
In-Reply-To: <20240131123238.2332064-1-zhangqiao22@huawei.com>
Zhang Qiao <zhangqiao22@huawei.com> writes:
> RT_RUNTIME_SHARE is an important strategy for rt bandwidth, and
> we should document this sched feature.
>
> Signed-off-by: Zhang Qiao <zhangqiao22@huawei.com>
> ---
> Documentation/scheduler/sched-rt-group.rst | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/Documentation/scheduler/sched-rt-group.rst b/Documentation/scheduler/sched-rt-group.rst
> index d685609ed3d7..4d8eceb71f5e 100644
> --- a/Documentation/scheduler/sched-rt-group.rst
> +++ b/Documentation/scheduler/sched-rt-group.rst
> @@ -12,6 +12,7 @@ Real-Time group scheduling
> 2.1 System-wide settings
> 2.2 Default behaviour
> 2.3 Basis for grouping tasks
> + 2.4 RT_RUNTIME_SHARE sched feature
> 3. Future plans
>
>
> @@ -146,6 +147,16 @@ For now, this can be simplified to just the following (but see Future plans):
>
> \Sum_{i} runtime_{i} <= global_runtime
>
> +2.4 RT_RUNTIME_SHARE sched feature
> +----------------------------
> +
> +RT_RUNTIME_SHARE allows a cpu borrows rt-runtime from other cpus if it runs
> +out of its own rt-runtime.
> +
> +With this feature enabled, a rt-task probably hits 100% cpu usage and starves
> +per-cpu tasks like kworkers, as a result, it may hang up the whole system.
> +Therefore, in order to avoid such exception, recommand to disable this feature
> +by default unless you really know what you're up to.
So this doesn't appear to have been picked up by anybody...should I
carry it in docs, or is there some other reason why it hasn't gone in?
Thanks,
jon
next prev parent reply other threads:[~2024-02-28 22:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 12:32 [PATCH] sched/Documentation: Add RT_RUNTIME_SHARE documentation Zhang Qiao
2024-02-28 22:44 ` Jonathan Corbet [this message]
2024-03-24 3:54 ` Zhang Qiao
2024-04-09 7:25 ` Zhang Qiao
2024-04-12 2:50 ` Bagas Sanjaya
2024-04-19 8:51 ` Zhang Qiao
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=875xy8p5tt.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=chrubis@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=zhangqiao22@huawei.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).