From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>,
isar-users <isar-users@googlegroups.com>,
"Larson, Chris" <Chris_Larson@mentor.com>
Subject: Re: bitbake multiconfig pipeline serialization
Date: Mon, 5 Feb 2018 14:41:34 +0100 [thread overview]
Message-ID: <8713b76c-ba16-dc93-2cf9-a432c7f26c05@siemens.com> (raw)
In-Reply-To: <85e28a77-1e98-2031-8405-9f9bc58fb482@ilbers.de>
On 2018-02-05 14:38, Alexander Smirnov wrote:
> Hi all,
>
> I've noticed some undesired behavior in bitbake using multiconfig - it
> never runs the same recipe:task in parallel for different configurations.
>
> For example:
> - You are going to build 'arm-jessie' and 'x86-jessie'.
> - Task buildchroot:do_rootfs will be serialized, for example 'arm' will
> be completed first and *only* then 'x86' will be started.
>
> I see no technical issues to run them in parallel in Isar, because we
> have completely split multiconfigs in our 'tmp/work' directory.
>
> I've briefly checked bitbake 'git log' and found some commits that could
> somehow related to this serialization:
>
> - 937acf267fa9e45f538695b2cf8aa83232a96240
> - a9041fc96a14e718c0c1d1676e705343b9e872d3
>
> So if somebody knows more details about this issue, I'll be happy to see
> them here :-)
>
Chris, can you enlighten us?
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2018-02-05 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 13:38 Alexander Smirnov
2018-02-05 13:41 ` 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=8713b76c-ba16-dc93-2cf9-a432c7f26c05@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Chris_Larson@mentor.com \
--cc=asmirnov@ilbers.de \
--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