mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zhang Qiao <zhangqiao22@huawei.com>
To: <mingo@kernel.org>, <chrubis@suse.cz>, <rostedt@goodmis.org>,
	<bagasdotme@gmail.com>, <corbet@lwn.net>
Cc: <linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] sched/Documentation: Add RT_RUNTIME_SHARE documentation
Date: Mon, 27 May 2024 11:13:31 +0800	[thread overview]
Message-ID: <3dffcc67-750e-c4c4-9154-99f1b1154fe0@huawei.com> (raw)
In-Reply-To: <20240419090432.1935211-1-zhangqiao22@huawei.com>

Ping.

在 2024/4/19 17:04, Zhang Qiao 写道:
> 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>
> Improvements-suggested-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
>  Documentation/scheduler/sched-rt-group.rst | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 
> diff --git a/Documentation/scheduler/sched-rt-group.rst b/Documentation/scheduler/sched-rt-group.rst
> index d685609ed3d7..eea2fc6f068f 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,17 @@ 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 to borrow rt-runtime from other cpus if it runs
> +out of its own rt-runtime.
> +
> +With this feature enabled, a rt-task may hit 100% cpu usage and can stall other
> +per-cpu tasks like kworkers, as a result, which leads into system hang.
> +
> +Thus, it is advised to disable this feature by default to avoid aforementioned
> +issue unless you know what you're doing.
>  
>  3. Future plans
>  ===============
> 

      parent reply	other threads:[~2024-05-27  3:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19  9:04 Zhang Qiao
2024-04-19 11:56 ` Bagas Sanjaya
2024-05-27  3:13 ` Zhang Qiao [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=3dffcc67-750e-c4c4-9154-99f1b1154fe0@huawei.com \
    --to=zhangqiao22@huawei.com \
    --cc=bagasdotme@gmail.com \
    --cc=chrubis@suse.cz \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®