[PATCH] doc: Mention OE routine for setting BB_NUMBER_THREADS

[PATCH] doc: Mention OE routine for setting BB_NUMBER_THREADS

[Robert P. J. Day]

Given the discussion of BB_NUMBER_THREADS, what it means and how to
set it, it seems only fair to mention that it's probably already set.

Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>

---

diff --git a/doc/bitbake-user-manual/bitbake-user-manual-execution.rst b/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
index d74e768f..a2003997 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
+++ b/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
@@ -45,6 +45,13 @@ the BitBake command and its options, see ":ref:`The BitBake Command
    A possibly simpler solution is that some Linux distributions (e.g.
    Debian and Ubuntu) provide the ``ncpus`` command.

+   If you're using a relatively recent version of Poky or Openembedded,
+   the provided ``bitbake.conf`` file already comes with a call to an OE
+   utility routine that does this calculation for you::
+
+     # Default to setting automatically based on cpu count
+     BB_NUMBER_THREADS ?= "${@oe.utils.cpu_count()}"
+
 Parsing the Base Configuration Metadata
 =======================================


-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                         http://crashcourse.ca

LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: [bitbake-devel] [PATCH] doc: Mention OE routine for setting BB_NUMBER_THREADS

[Khem Raj]

On Wed, Mar 17, 2021 at 3:34 AM Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>
> Given the discussion of BB_NUMBER_THREADS, what it means and how to
> set it, it seems only fair to mention that it's probably already set.
>
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>
> ---
>
> diff --git a/doc/bitbake-user-manual/bitbake-user-manual-execution.rst b/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
> index d74e768f..a2003997 100644
> --- a/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
> +++ b/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
> @@ -45,6 +45,13 @@ the BitBake command and its options, see ":ref:`The BitBake Command
>     A possibly simpler solution is that some Linux distributions (e.g.
>     Debian and Ubuntu) provide the ``ncpus`` command.
>
> +   If you're using a relatively recent version of Poky or Openembedded,

I think it would be better to avoid distro names in generic documentation

> +   the provided ``bitbake.conf`` file already comes with a call to an OE
> +   utility routine that does this calculation for you::
> +
> +     # Default to setting automatically based on cpu count
> +     BB_NUMBER_THREADS ?= "${@oe.utils.cpu_count()}"
> +
>  Parsing the Base Configuration Metadata
>  =======================================
>
>
> --
>
> ========================================================================
> Robert P. J. Day                                 Ottawa, Ontario, CANADA
>                          http://crashcourse.ca
>
> LinkedIn:                               http://ca.linkedin.com/in/rpjday
> ========================================================================
>
> 
>

Re: [bitbake-devel] [PATCH] doc: Mention OE routine for setting BB_NUMBER_THREADS

[Robert P. J. Day]

On Wed, 17 Mar 2021, Khem Raj wrote:

> On Wed, Mar 17, 2021 at 3:34 AM Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> >
> > Given the discussion of BB_NUMBER_THREADS, what it means and how to
> > set it, it seems only fair to mention that it's probably already set.
> >
> > Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
> >
> > ---
> >
> > diff --git a/doc/bitbake-user-manual/bitbake-user-manual-execution.rst b/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
> > index d74e768f..a2003997 100644
> > --- a/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
> > +++ b/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
> > @@ -45,6 +45,13 @@ the BitBake command and its options, see ":ref:`The BitBake Command
> >     A possibly simpler solution is that some Linux distributions (e.g.
> >     Debian and Ubuntu) provide the ``ncpus`` command.
> >
> > +   If you're using a relatively recent version of Poky or Openembedded,
>
> I think it would be better to avoid distro names in generic documentation

... snip ...

  normally, i'd agree, but given that 99.4237 per cent of bitbake
usage is in the context of OE or YP, if you're going to tell people
about BB_NUMBER_THREADS, it is not out of line to point out that they
almost certainly have that value calculated for them automatically
already.

rday

Re: [bitbake-devel] [PATCH] doc: Mention OE routine for setting BB_NUMBER_THREADS

[Khem Raj]

On Wed, Mar 17, 2021 at 8:56 AM Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>
> On Wed, 17 Mar 2021, Khem Raj wrote:
>
> > On Wed, Mar 17, 2021 at 3:34 AM Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> > >
> > > Given the discussion of BB_NUMBER_THREADS, what it means and how to
> > > set it, it seems only fair to mention that it's probably already set.
> > >
> > > Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
> > >
> > > ---
> > >
> > > diff --git a/doc/bitbake-user-manual/bitbake-user-manual-execution.rst b/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
> > > index d74e768f..a2003997 100644
> > > --- a/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
> > > +++ b/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
> > > @@ -45,6 +45,13 @@ the BitBake command and its options, see ":ref:`The BitBake Command
> > >     A possibly simpler solution is that some Linux distributions (e.g.
> > >     Debian and Ubuntu) provide the ``ncpus`` command.
> > >
> > > +   If you're using a relatively recent version of Poky or Openembedded,
> >
> > I think it would be better to avoid distro names in generic documentation
>
> ... snip ...
>
>   normally, i'd agree, but given that 99.4237 per cent of bitbake
> usage is in the context of OE or YP, if you're going to tell people
> about BB_NUMBER_THREADS, it is not out of line to point out that they
> almost certainly have that value calculated for them automatically
> already.

OpenEmbedded is perhaps more appropriate here, since its the build
system and would tend to cover all
OE based distributions including poky

>
> rday

Re: [bitbake-devel] [PATCH] doc: Mention OE routine for setting BB_NUMBER_THREADS

[Robert P. J. Day]

On Wed, 17 Mar 2021, Khem Raj wrote:

> On Wed, Mar 17, 2021 at 8:56 AM Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> >
> > On Wed, 17 Mar 2021, Khem Raj wrote:
> >
> > > On Wed, Mar 17, 2021 at 3:34 AM Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> > > >
> > > > Given the discussion of BB_NUMBER_THREADS, what it means and how to
> > > > set it, it seems only fair to mention that it's probably already set.
> > > >
> > > > Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
> > > >
> > > > ---
> > > >
> > > > diff --git a/doc/bitbake-user-manual/bitbake-user-manual-execution.rst b/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
> > > > index d74e768f..a2003997 100644
> > > > --- a/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
> > > > +++ b/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
> > > > @@ -45,6 +45,13 @@ the BitBake command and its options, see ":ref:`The BitBake Command
> > > >     A possibly simpler solution is that some Linux distributions (e.g.
> > > >     Debian and Ubuntu) provide the ``ncpus`` command.
> > > >
> > > > +   If you're using a relatively recent version of Poky or Openembedded,
> > >
> > > I think it would be better to avoid distro names in generic documentation
> >
> > ... snip ...
> >
> >   normally, i'd agree, but given that 99.4237 per cent of bitbake
> > usage is in the context of OE or YP, if you're going to tell people
> > about BB_NUMBER_THREADS, it is not out of line to point out that they
> > almost certainly have that value calculated for them automatically
> > already.
>
> OpenEmbedded is perhaps more appropriate here, since its the build
> system and would tend to cover all
> OE based distributions including poky

  i'm good with that, will re-submit.

rday