public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: quentin.schulz@theobroma-systems.com,
	Paul Eggleton <paul.eggleton@microsoft.com>
Cc: docs@lists.yoctoproject.org, bitbake-devel@lists.openembedded.org
Subject: Re: [docs] [PATCH] doc: bitbake-user-manual: expand description of BB_PRESSURE_MAX variables
Date: Wed, 12 Oct 2022 14:58:36 +0200	[thread overview]
Message-ID: <8f2ef282-75d0-18b7-52ad-bc7f2e25552b@bootlin.com> (raw)
In-Reply-To: <91b7e8e3-a6b9-d426-527a-368e5676d4ea@theobroma-systems.com>

Hi Quentin,

On 10/12/22 14:52, Quentin Schulz via lists.yoctoproject.org wrote:
> Hi Michael, Paul,
>
> On 10/12/22 14:43, Michael Opdenacker via lists.yoctoproject.org wrote:
>> From: Michael Opdenacker <michael.opdenacker@bootlin.com>
>>
>> Signed-off-by: Paul Eggleton <paul.eggleton@microsoft.com>
>> Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
>> ---
>>   .../bitbake-user-manual-ref-variables.rst     | 60 +++++++++++++------
>>   1 file changed, 43 insertions(+), 17 deletions(-)
>>
>> 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 725e6c2c..b9c1b75d 100644
>> --- a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
>> +++ b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
>> @@ -484,29 +484,55 @@ overview of their function and contents.
>>            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::
>> +      Specifies a maximum CPU pressure threshold, above which BitBake's
>> +      scheduler will not start new tasks (providing there is at least
>> +      one active task). If no value is set, CPU pressure is not
>> +      monitored when starting tasks.
>> +
>> +      The pressure data is calculated based upon what (recent) Linux
>
> "recent" does not mean much. Can we remove this or get a minimal 
> version number?

Very good point!
/proc/pressure was introduced in Linux 4.20 
(https://kernelnewbies.org/Linux_4.20#Pressure_stall_information_for_better_overview_of_system_load)

I'm sending an update soon.
Thanks again

Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



      reply	other threads:[~2022-10-12 12:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12 12:43 [PATCH] doc: bitbake-user-manual: expand description of BB_PRESSURE_MAX variables michael.opdenacker
2022-10-12 12:52 ` [docs] " Quentin Schulz
2022-10-12 12:58   ` 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=8f2ef282-75d0-18b7-52ad-bc7f2e25552b@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=docs@lists.yoctoproject.org \
    --cc=paul.eggleton@microsoft.com \
    --cc=quentin.schulz@theobroma-systems.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