From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] MAKEALL: Fix kill_children
Date: Wed, 31 Oct 2012 20:02:10 -0700 [thread overview]
Message-ID: <20121101030210.GF24095@bill-the-cat> (raw)
In-Reply-To: <201211010332.30447.marek.vasut@gmail.com>
On Thu, Nov 01, 2012 at 03:32:30AM +0100, Marek Vasut wrote:
> Dear Joe Hershberger,
>
> > When building in parallel, make sure that we look up the children
> > based on the the actual process group id instead of just assuming
> > that the MAKEALL pid is the process group id.
> >
> > Also ensure that logs from incomplete builds are deleted in the
> > process.
> >
> > Signed-off-by: Joe Hershberger <joe.hershberger@ni.com>
> [...]
>
> Nice $subject.
>
> btw. is it possible to improve the u-boot build process parallelization?
Probably a little, but not a lot? It's be interesting to profile and
see where a single machine build has bottlenecks, if any.
--
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/4bf34f00/attachment.pgp>
next prev parent reply other threads:[~2012-11-01 3:02 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 [this message]
2012-11-01 4:14 ` Andy Fleming
2012-11-01 14:35 ` Marek Vasut
2012-11-01 15:23 ` Tom Rini
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=20121101030210.GF24095@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 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.