From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] WIP: Test version of buildman - U-Boot builder
Date: Wed, 31 Oct 2012 18:18:32 -0700 [thread overview]
Message-ID: <20121101011832.GC24095@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ2-wpd=Eq9qnwbvtbbM8tCjCLG8XddHePFCF9fbuVFj4A@mail.gmail.com>
On Wed, Oct 31, 2012 at 05:11:51PM -0700, Simon Glass wrote:
[snip]
> Also rather than running with 'make -j40' or whatever, it uses 'make
> -j1' but with 40 threads. This increases CPU utilisation quite
> substantially (almost 50%) - I think this was discussed some time ago,
MAKEALL supports this, but doesn't default to it, today. I'm wondering
if we ought to make it the default for all non-single board builds. The
winning point is right around boards-to-build == `grep -c processor
/proc/cpuinfo` and I think is right around setting NBUILDS to that
value, both on consumer multicore and heavy-duty 32/64 core boxes.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20121031/9134fd62/attachment.pgp>
next prev parent reply other threads:[~2012-11-01 1:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 21:25 [U-Boot] [PATCH 1/2] WIP: Changes to patman libraries Simon Glass
2012-10-31 21:25 ` [U-Boot] [PATCH 2/2] WIP: Test version of buildman - U-Boot builder Simon Glass
2012-10-31 22:46 ` Wolfgang Denk
2012-10-31 22:51 ` Tom Rini
2012-10-31 23:08 ` Simon Glass
2012-10-31 23:37 ` Wolfgang Denk
2012-11-01 0:11 ` Simon Glass
2012-11-01 1:18 ` Tom Rini [this message]
2012-11-01 4:17 ` Andy Fleming
2012-11-01 21:01 ` Simon Glass
2012-11-01 23:29 ` Tom Rini
2012-12-01 20:55 ` Simon Glass
2012-10-31 22:42 ` [U-Boot] [PATCH 1/2] WIP: Changes to patman libraries Wolfgang Denk
2012-10-31 23:12 ` Simon Glass
2012-10-31 23:40 ` Wolfgang Denk
2012-11-01 0:04 ` Simon Glass
2012-11-01 20:59 ` Simon Glass
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=20121101011832.GC24095@bill-the-cat \
--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