From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: BitBake developer list <bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH] bitbake-user-manual-execution.xml: Update parallelization note.
Date: Wed, 18 Jun 2014 16:52:07 +0100 [thread overview]
Message-ID: <1403106727.2104.72.camel@ted> (raw)
In-Reply-To: <alpine.LFD.2.11.1406181120030.29194@localhost>
On Wed, 2014-06-18 at 11:22 -0400, Robert P. J. Day wrote:
> Update the note to explain that current versions of BitBake
> automatically calculate the proper values for BB_NUMBER_THREADS
The current version of bitbake doesn't though.
There is an *OE* helper function which the default local.conf files use.
Cheers,
Richard
> and
> PARALLEL_MAKE so you no longer need to set those values manually.
>
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>
> ---
>
> diff --git a/doc/bitbake-user-manual/bitbake-user-manual-execution.xml b/doc/bitbake-user-manual/bitbake-user-manual-execution.xml
> index 8514f23..6d49fb6 100644
> --- a/doc/bitbake-user-manual/bitbake-user-manual-execution.xml
> +++ b/doc/bitbake-user-manual/bitbake-user-manual-execution.xml
> @@ -29,11 +29,23 @@
> </para>
>
> <note>
> - Prior to executing BitBake, you should take advantage of parallel
> - thread execution by setting the
> - <link linkend='var-BB_NUMBER_THREADS'><filename>BB_NUMBER_THREADS</filename></link>
> - variable in your <filename>local.conf</filename>
> - configuration file.
> + In order to take advantage of parallel thread execution on your build
> + host, earlier versions of BitBake recommended setting the following
> + variables in your project's <filename>local.conf</filename> file,
> + based on your host's number of CPUs or multithreading
> + capability:
> + <literallayout class='monospaced'>
> + BB_NUMBER_THREADS ?= ...
> + PARALLEL_MAKE ?= ...
> + </literallayout>
> + The current version of BitBake now handles this automatically by
> + assigning default values to those variables as follows:
> + <literallayout class='monospaced'>
> + BB_NUMBER_THREADS ?= "${@oe.utils.cpu_count()}"
> + PARALLEL_MAKE ?= "-j ${@oe.utils.cpu_count()}"
> + </literallayout>
> + so you no longer need to worry about this, unless you specifically
> + want to override this for some reason.
> </note>
>
> <section id='parsing-the-base-configuration-metadata'>
>
> --
>
> ========================================================================
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
>
> Twitter: http://twitter.com/rpjday
> LinkedIn: http://ca.linkedin.com/in/rpjday
> ========================================================================
next prev parent reply other threads:[~2014-06-18 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 15:22 [PATCH] bitbake-user-manual-execution.xml: Update parallelization note Robert P. J. Day
2014-06-18 15:52 ` Richard Purdie [this message]
2014-06-18 15:57 ` Robert P. J. Day
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=1403106727.2104.72.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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