On Fri, Sep 23, 2016 at 03:09:53PM -0600, Simon Glass wrote: > Hi Tom, > > On 23 September 2016 at 12:42, Tom Rini <tr...@konsulko.com> wrote: > > On Thu, Sep 22, 2016 at 10:14:01PM -0600, Simon Glass wrote: > >> Hi Tom, > >> > >> On 19 September 2016 at 13:14, Tom Rini <tr...@konsulko.com> wrote: > >> > On Sun, Sep 18, 2016 at 04:48:31PM -0600, Simon Glass wrote: > >> > > >> >> On a machine with a lot of CPUs this prints a lot of useless lines of > >> >> the > >> >> form: > >> >> > >> >> Cloning repo for thread <n> > >> >> > >> >> Adjust the output so that these all appear on one line, and disappear > >> >> when > >> >> the cloning is complete. > >> >> > >> >> Note: This cloning is actually unnecessary and very wasteful on disk > >> >> space > >> >> (about 3.5GB each time). It would be better to create symlinks. > >> > > >> > When do we actually need to clone? Or why, even? > >> > >> Each thread can check out a different commit. I think it might be > >> possible to put the checkout in a separate thread so it can avoid > >> contention. I'm not quite sure... > > > > Ah, ok. So we have a few places under tools/ that should be doing 'git > > clone --local', at first glance. > > Actually I think I am wrong about this. The 3.5GB is due to 32 copies > of the code, not the cloning. In fact --local is the default and that > is what buildman seems to use. > > So in fact I'm not sure we can change it. Each thread can be building > a different commit.
Ah, OK, oh well. -- Tom
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
