From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] MAKEALL: Fix kill_children
Date: Thu, 1 Nov 2012 08:23:35 -0700 [thread overview]
Message-ID: <509293F7.9080407@ti.com> (raw)
In-Reply-To: <201211011535.19205.marex@denx.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/01/12 07:35, Marek Vasut wrote:
> Dear Andy Fleming,
>
>> On Wed, Oct 31, 2012 at 9:32 PM, Marek Vasut
>> <marek.vasut@gmail.com> wrote:
[snip]
>>> btw. is it possible to improve the u-boot build process
>>> parallelization?
>>
>> In what way?
>
> I recall someone complained the build process wasn't
> parallelizable enough and thus we need this stuff to run multiple
> builds at once in MAKEALL.
I don't know if the first half of that statement is strictly true.
It'd be interesting to profile a build on one of the very large boxes
but I think the issue is we only have ~300 objects being built. It's
hard to run up a load of 32 when you only have that many things to
build. But multiplying that by the number of boards in a arch or some
cpu or soc combinations is easier to run up the load, except around
the tails. But, profiling, please!
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQIcBAEBAgAGBQJQkpP3AAoJENk4IS6UOR1WkQgP/0oih/weogNgs7Ql9Iv4Ct06
pNlaYJiDEOlKxhdwG80zXnyWSqIKkLIYN09N5NPyYQ3qgeM+uRYRiReDiwudYY+P
pkOBWudj4X8SWUOucbRVWgx89DU4VrxCzY7sqqhDsQ+5ZTz8UjwG4wZaZOdewdLr
ktxe90NQGVsl6ozQtJoSoJ57y727e07piGuBISRDwYZPwmpCl8d9dNd6liRf7zdv
EXLIbO9aLROD67pkpO9OY392CVAU7cO4p5ir0dTGVZfYdPpadM+/Jsay5KsPhCf0
rM4eAFG1BvqhMBCc2NyPH2P71YU6rEsPdH6DyNh10aDRwUd7eep6/pU0tKbYpUR4
z0nsE1QOVLD5DY43/N0fEMN2G62LMiwnPuEQWT89N9uyDaFP7SS8lLRp/Sj7EhQF
NLEMtMKvN8bVIBiVFXW8WOVRJqlc5uVpoeRqfbOctl50x9zGNHhypJlH65qtEeg/
UlroM1tw3p0j6Xk9zrNioGFy5/mpkF1hw2pirUAKF06yomg0FM9oAOwp/tfjyjgU
uU2myW+lgWk0VfW/H00fyEBBs3vPnLo1PSL2WUKg43WRiEdY5C0/+E+lSIN7ph/z
eeWKelSu6BUWPkuqBnxhUkMFRYtPCNqE5x6BdVv5p8TPxacD842qDP930Vg3YhqQ
1KG0rtSB69QqzAtVYDmO
=4XRP
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-11-01 15:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 1:55 [U-Boot] [PATCH 1/2] MAKEALL: Fix kill_children Joe Hershberger
2012-10-31 1:55 ` [U-Boot] [PATCH 2/2] MAKEALL: Add options for incremental building Joe Hershberger
2012-10-31 20:22 ` Simon Glass
2012-12-07 15:50 ` Tom Rini
2012-10-31 20:21 ` [U-Boot] [PATCH 1/2] MAKEALL: Fix kill_children Simon Glass
2012-11-01 2:32 ` Marek Vasut
2012-11-01 3:02 ` Tom Rini
2012-11-01 4:14 ` Andy Fleming
2012-11-01 14:35 ` Marek Vasut
2012-11-01 15:23 ` Tom Rini [this message]
2012-11-03 22:54 ` Tom Rini
2012-11-05 0:13 ` Joe Hershberger
2012-11-05 0:53 ` Tom Rini
2012-12-07 15:50 ` Tom Rini
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=509293F7.9080407@ti.com \
--to=trini@ti.com \
--cc=u-boot@lists.denx.de \
/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