From: michael.opdenacker@bootlin.com
To: bitbake-devel@lists.openembedded.org
Cc: docs@lists.yoctoproject.org,
Michael Opdenacker <michael.opdenacker@bootlin.com>,
Aryaman Gupta <aryaman.gupta@windriver.com>,
Randy Macleod <Randy.Macleod@windriver.com>,
Quentin Schulz <foss+yocto@0leil.net>
Subject: [PATCH RESEND v3] doc: bitbake-user-manual: Add definition for BB_PRESSURE_MAX variables
Date: Mon, 19 Sep 2022 16:58:12 +0200 [thread overview]
Message-ID: <20220919145812.38756-1-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <17111BB47189E793.5304@lists.yoctoproject.org>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
From: Aryaman Gupta <aryaman.gupta@windriver.com>
Add the definitions for the BB_PRESSURE_MAX{CPU|IO|MEMORY} variables in the
bitbake varibales glossary. Further information on how to determine a good
threshold will be added to the Yocto reference manual in a later commit.
Signed-off-by: Aryaman Gupta <aryaman.gupta@windriver.com>
Signed-off-by: Randy Macleod <Randy.Macleod@windriver.com>
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reviewed-by: Quentin Schulz <foss+yocto@0leil.net>
---
Changes in V3 (Michael Opdenacker):
- Remove reference to Yocto Project manual, not documenting
the variables yet.
- Fix a typo ("it's" -> "its")
- Simplify syntax (":" followed by "::" replaced by "::"
---
.../bitbake-user-manual-ref-variables.rst | 25 +++++++++++++++++++
1 file changed, 25 insertions(+)
diff --git a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
index 12aef3cb..725e6c2c 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
+++ b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
@@ -483,6 +483,31 @@ overview of their function and contents.
You must set this variable in the external environment in order
for it to work.
+ :term:`BB_PRESSURE_MAX_CPU`
+ The threshold for maximum CPU pressure before BitBake prevents the
+ scheduling of new tasks. Once the :term:`BB_PRESSURE_MAX_CPU` threshold
+ is exceeded, new tasks are not started until the pressure subsides to
+ below the threshold. If :term:`BB_PRESSURE_MAX_CPU` is not set, CPU
+ pressure is not monitored. A threshold can be set in ``conf/local.conf``
+ as::
+
+ BB_PRESSURE_MAX_CPU = "500"
+
+ :term:`BB_PRESSURE_MAX_IO`
+ The threshold for maximum IO pressure experienced before BitBake
+ prevents the scheduling of new tasks. The IO pressure is regulated in the
+ same way as :term:`BB_PRESSURE_MAX_CPU`. At this point in time,
+ experiments show that IO pressure tends to be short-lived and regulating
+ just the CPU can help to reduce it.
+
+ :term:`BB_PRESSURE_MAX_MEMORY`
+ The threshold for maximum memory pressure experienced before BitBake
+ prevents the scheduling of new tasks. The memory pressure is regulated in
+ the same way as :term:`BB_PRESSURE_MAX_CPU`. Note that any memory
+ pressure indicates that a system is being pushed beyond its capacity. At
+ this point in time, experiments show that memory pressure tends to be
+ short-lived and regulating just the CPU can help to reduce it.
+
:term:`BB_RUNFMT`
Specifies the name of the executable script files (i.e. run files)
saved into ``${``\ :term:`T`\ ``}``. By default, the
--
2.34.1
parent reply other threads:[~2022-09-19 14:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <17111BB47189E793.5304@lists.yoctoproject.org>]
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=20220919145812.38756-1-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=Randy.Macleod@windriver.com \
--cc=aryaman.gupta@windriver.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=docs@lists.yoctoproject.org \
--cc=foss+yocto@0leil.net \
/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