From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: bitbake-devel@lists.openembedded.org,
YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [bitbake-devel] [PATCH] doc/user-manual: Add BB_LOADFACTOR_MAX
Date: Thu, 11 Apr 2024 15:50:02 +0200 [thread overview]
Message-ID: <15a8400a-37b6-4216-96a2-1ba5d48654d6@bootlin.com> (raw)
In-Reply-To: <20240411122508.2149106-1-richard.purdie@linuxfoundation.org>
Hi Richard,
On 4/11/24 at 14:25, Richard Purdie wrote:
> Document BB_LOADFACTOR_MAX which was recently added.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
> .../bitbake-user-manual-ref-variables.rst | 9 +++++++++
> 1 file changed, 9 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 d3936935cd..00faeea686 100644
> --- a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
> +++ b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
> @@ -432,6 +432,15 @@ overview of their function and contents.
> ``ConfigParsed`` event can set the variable to trigger the re-parse.
> You must be careful to avoid recursive loops with this functionality.
>
> + :term:`BB_LOADFACTOR_MAX`
> + Setting this to a value will cause bitbake to check the system load
s/bitbake/BitBake/
That's the convention we follow everywhere, when talking about the
total, not the command to type of course.
> + average before executing new tasks. If the load average is above the
> + the number of CPUs multipled by this factor, no new task will be started
> + unless there is no task executing. A value of "1.5" has been found to
> + work reasonably. This is helpful for systems which don't have pressure
> + regulation enabled, which is more granular. Pressure values take
> + precedence over loadfactor.
> +
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Once this is merged, I'll make the YP docs directly point to this in the
BitBake manual. At the moment, we have a shorter description.
Thanks!
Michael
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2024-04-11 13:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 12:25 [PATCH] doc/user-manual: Add BB_LOADFACTOR_MAX Richard Purdie
2024-04-11 13:50 ` Michael Opdenacker [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=15a8400a-37b6-4216-96a2-1ba5d48654d6@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=docs@lists.yoctoproject.org \
--cc=richard.purdie@linuxfoundation.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 read-only IMAP folder(s) and NNTP newsgroup(s).