From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 7/7] automatically set PARALLEL_JOBS when BR2_JLEVEL is 0
Date: Thu, 14 Jun 2012 08:07:36 +0200 [thread overview]
Message-ID: <87ipeuwhnb.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1339631041.32578.9.camel@doorstop.aus.2wire.com> (Nathan Lynch's message of "Wed, 13 Jun 2012 18:44:01 -0500")
>>>>> "Nathan" == Nathan Lynch <ntl@pobox.com> writes:
>> In my experience, you need 2 times the number of CPUs to fully utilize
>> the processor because most compilations have long iowait latencies.
Nathan> Yeah. I'm happy to make this change, assuming others agree?
I was going to say something like that as well, so yes please.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-06-14 6:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 2:09 [Buildroot] [PATCH 0/7] automatically determine job concurrency Nathan Lynch
2012-06-12 2:09 ` [Buildroot] [PATCH 1/7] introduce PARALLEL_JOBS build system variable Nathan Lynch
2012-06-12 2:09 ` [Buildroot] [PATCH 2/7] boost: change uses of BR2_JLEVEL to PARALLEL_JOBS Nathan Lynch
2012-06-12 2:09 ` [Buildroot] [PATCH 3/7] cmake: change use " Nathan Lynch
2012-06-12 2:09 ` [Buildroot] [PATCH 4/7] midori: " Nathan Lynch
2012-06-12 2:09 ` [Buildroot] [PATCH 5/7] qt: " Nathan Lynch
2012-06-12 2:09 ` [Buildroot] [PATCH 6/7] toolchain/crosstool-ng: " Nathan Lynch
2012-06-12 2:09 ` [Buildroot] [PATCH 7/7] automatically set PARALLEL_JOBS when BR2_JLEVEL is 0 Nathan Lynch
2012-06-13 23:27 ` Arnout Vandecappelle
2012-06-13 23:44 ` Nathan Lynch
2012-06-14 6:07 ` Peter Korsgaard [this message]
2012-06-14 6:16 ` Nathan Lynch
2012-06-14 8:56 ` Peter Korsgaard
2012-06-14 8:33 ` Richard Braun
2012-06-14 15:02 ` [Buildroot] [PATCHv2 " Nathan Lynch
2012-06-14 18:09 ` Baruch Siach
2012-06-16 19:37 ` [Buildroot] [PATCHv3 " Nathan Lynch
2012-06-24 9:13 ` [Buildroot] [PATCH 0/7] automatically determine job concurrency Peter Korsgaard
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=87ipeuwhnb.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.