From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] u-boot-custom: Fix parallel build
Date: Tue, 2 Oct 2018 11:34:29 +0200 [thread overview]
Message-ID: <7c8dbdbe-b40d-19f8-8085-a0910abb3672@siemens.com> (raw)
In-Reply-To: <20181002113104.54503304@md1pvb1c.ad001.siemens.net>
On 02.10.18 11:31, Henning Schild wrote:
> Am Tue, 2 Oct 2018 00:15:55 +0200
> schrieb "[ext] Jan Kiszka" <jan.kiszka@siemens.com>:
>
>> Do to missing "echo", we were running with "-j" so far, and the build
>> log contained some complains about unknown commands.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>> meta/recipes-bsp/u-boot/files/debian/rules | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-bsp/u-boot/files/debian/rules
>> b/meta/recipes-bsp/u-boot/files/debian/rules index deb7c8e..1d9e645
>> 100755 --- a/meta/recipes-bsp/u-boot/files/debian/rules
>> +++ b/meta/recipes-bsp/u-boot/files/debian/rules
>> @@ -12,7 +12,7 @@ export CROSS_COMPILE=$(DEB_HOST_GNU_TYPE)-
>> SET_CROSS_BUILD_TOOLS=CROSS_BUILD_TOOLS=y
>> endif
>>
>> -PARALLEL_BUILD=-j $(shell $$(($$(nproc) * 2)))
>> +PARALLEL_BUILD=-j $(shell echo $$(($$(nproc) * 2)))
>
> Why the "*2", usually nproc or nproc+1 should be what you want. And in
> that case "nproc" is simpler to script.
You usually do 2-times overcommitment with such workloads to ensure that no
single CPU is idling because of I/O delays.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2018-10-02 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 22:15 Jan Kiszka
2018-10-02 9:31 ` Henning Schild
2018-10-02 9:34 ` Jan Kiszka [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=7c8dbdbe-b40d-19f8-8085-a0910abb3672@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.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