OK, I would say use a "-j" if that is not already in use, to be similar to make's job parallelism option.
On Wed, Aug 14, 2013 at 3:25 PM, Rempel, Cynthia <cynt6...@vandals.uidaho.edu> wrote: >>________________________________________ >>From: ged...@gwmail.gwu.edu [ged...@gwmail.gwu.edu] on behalf of Gedare Bloom >>[ged...@rtems.org] >>Sent: Wednesday, August 14, 2013 11:05 AM >>To: Rempel, Cynthia >>Cc: rtems-devel@rtems.org >>Subject: Re: [PATCH] parallelize bootstrap >> >>Hi, >> >>Would it be better to add an option to specify the maximum number of >>parallel jobs to run? Also, is it 10 jobs or 20 jobs maximum right >>now? I think there can be up to 10 controlled by n_confs, and up to 10 >>controlled by n_reconfs? > > It might be better to make it configurable... maybe someone would want it to > be just 1? I could add a wait after each for loop to limit it to 10 instead > of 10 each... > Thanks for the review! I'll make the change and resubmit :) > >> >>-Gedare >> >>On Fri, Aug 2, 2013 at 2:49 AM, Rempel, Cynthia >><cynt6...@vandals.uidaho.edu> wrote: >>> Hi, >>> >>> Applying this patch changes the for loops using autoconf into parallel for >>> loops calling autoconf. >>> It reduced the time to run bootstrap from ~9:30 to ~2:45 >>> It's limited to 10 sub shells working in parallel though... >>> I only checked that hello.exe and ticker.exe ran on sparc-rtems4.11-gdb... >>> >>> Thanks! >>> Cindy _______________________________________________ rtems-devel mailing list rtems-devel@rtems.org http://www.rtems.org/mailman/listinfo/rtems-devel
