From: Saul Wold <sgw@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] local.conf.sample: Suggest parallelism of twice the number of cores.
Date: Wed, 09 Jan 2013 10:31:47 -0800 [thread overview]
Message-ID: <50EDB793.7080202@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1301091312270.14396@oneiric>
On 01/09/2013 10:14 AM, Robert P. J. Day wrote:
>
> To be consistent with the Yocto Quick Start Guide, recommend that
> parallelism represent twice the number of cores on a multi-core
> machine.
>
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>
> ---
>
> diff --git a/meta/conf/local.conf.sample b/meta/conf/local.conf.sample
> index 859eb93..46187ce 100644
> --- a/meta/conf/local.conf.sample
> +++ b/meta/conf/local.conf.sample
> @@ -24,9 +24,9 @@
> #
> #PARALLEL_MAKE = "-j 4"
> #
> -# For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
> -# be appropriate for example.
> -
> +# If you have a multi-core machine, you would normally set both of these variables
> +# to twice the number of cores. So for a quad-core machine, it would be appropriate
> +# to set BB_NUMBER_THREADS = "8" and PARALLEL_MAKE = "-j 8".
I think adding a note to ensure that hyperthreading is enabled would be
appropriate, then number of threads = number of hyperthreaded cores (4
vs 8).
Sau!
> #
> # Machine Selection
> #
>
next prev parent reply other threads:[~2013-01-09 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 18:14 [PATCH] local.conf.sample: Suggest parallelism of twice the number of cores Robert P. J. Day
2013-01-09 18:31 ` Saul Wold [this message]
2013-01-09 18:43 ` Enrico Scholz
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=50EDB793.7080202@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@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