From: Kir Kolyshkin <kolyshkin@gmail.com>
To: corbet@lwn.net
Cc: linux-doc@vger.kernel.org, cgroups@vger.kernel.org,
Kir Kolyshkin <kolyshkin@gmail.com>
Subject: [PATCH 03/10] docs/scheduler/sched-bwc: fix note rendering
Date: Tue, 19 Jan 2021 16:18:17 -0800 [thread overview]
Message-ID: <20210120001824.385168-4-kolyshkin@gmail.com> (raw)
In-Reply-To: <20210120001824.385168-1-kolyshkin@gmail.com>
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
---
Documentation/scheduler/sched-bwc.rst | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/scheduler/sched-bwc.rst b/Documentation/scheduler/sched-bwc.rst
index 4af4ee1f3600..a44860d33ffc 100644
--- a/Documentation/scheduler/sched-bwc.rst
+++ b/Documentation/scheduler/sched-bwc.rst
@@ -2,8 +2,9 @@
CFS Bandwidth Control
=====================
-[ This document only discusses CPU bandwidth control for SCHED_NORMAL.
- The SCHED_RT case is covered in Documentation/scheduler/sched-rt-group.rst ]
+.. note::
+ This document only discusses CPU bandwidth control for SCHED_NORMAL.
+ The SCHED_RT case is covered in Documentation/scheduler/sched-rt-group.rst
CFS bandwidth control is a CONFIG_FAIR_GROUP_SCHED extension which allows the
specification of the maximum CPU bandwidth available to a group or hierarchy.
--
2.29.2
next prev parent reply other threads:[~2021-01-20 0:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 0:18 [PATCH 00/10] docs: cgroup nits and fixes Kir Kolyshkin
2021-01-20 0:18 ` [PATCH 01/10] docs/scheduler/sched-bwc: formatting fix Kir Kolyshkin
2021-01-20 0:18 ` [PATCH 02/10] docs/scheduler/sched-design-CFS: " Kir Kolyshkin
2021-01-20 0:18 ` Kir Kolyshkin [this message]
2021-01-20 0:18 ` [PATCH 04/10] docs/scheduler/sched-bwc: add proper ref Kir Kolyshkin
2021-01-20 17:43 ` Jonathan Corbet
2021-01-20 0:18 ` [PATCH 05/10] docs/scheduler/sched-bwc: note/link cgroup v2 Kir Kolyshkin
2021-01-20 0:18 ` [PATCH 06/10] docs/admin-guide: cgroup-v2: typos and spaces Kir Kolyshkin
2021-01-20 0:18 ` [PATCH 07/10] docs/admin-guide: cgroup-v2: fix cgroup.type rendering Kir Kolyshkin
2021-01-20 0:18 ` [PATCH 08/10] doc/admin-guide/cgroup-v2: use tables Kir Kolyshkin
2021-01-20 0:18 ` [PATCH 09/10] docs/admin-guide/cgroup-v2: nit Kir Kolyshkin
2021-01-20 0:18 ` [PATCH 10/10] docs/admin-guide/cgroup-v2: fix mount opt rendering Kir Kolyshkin
2021-01-20 16:43 ` [PATCH 00/10] docs: cgroup nits and fixes Tejun Heo
2021-01-21 18:42 ` Jonathan Corbet
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=20210120001824.385168-4-kolyshkin@gmail.com \
--to=kolyshkin@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.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).