From: Greg Dietsche <gregory.dietsche@cuw.edu>
To: Joe Perches <joe@perches.com>
Cc: julia@diku.dk, Gilles.Muller@lip6.fr, npalix.work@gmail.com,
rdunlap@xenotime.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, cocci@diku.dk
Subject: Re: [PATCH 3/3] coccicheck: add parallel execution
Date: Wed, 13 Jul 2011 21:14:34 -0500 [thread overview]
Message-ID: <4E1E510A.6010005@cuw.edu> (raw)
In-Reply-To: <1310524935.32558.8.camel@Joe-Laptop>
On 07/12/2011 09:42 PM, Joe Perches wrote:
> On Tue, 2011-07-12 at 20:26 -0500, Greg Dietsche wrote:
>
>> For example to process 6 SmPL patches at the same time:
>> make coccicheck PARALLEL=6
>> Results are held in /tmp until the scripts finish. By doing this the
>> script is able to collate the results from each SmPL patch instead of
>> interleaving them in the output.
>>
> You might try adding support for gnu parallel instead.
> http://www.gnu.org/software/parallel/
>
>
That is a very interesting and useful tool :) I'd never heard of it
before. The man page scares me a little bit - lots of options are marked
as "alpha testing," but the ones i tried seemed to work fine. Anyway,
without any modifications to Coccinelle, it is possible to do this:
ls scripts/coccinelle/*/*.cocci | parallel -j+0 make coccicheck COCCI={}
MODE=patch
it seems to behave mostly like my patch, but doesn't cleanup quite as
well if you decide to kill it with ctrl-c (it leaves instances of spatch
running). On the upside, it is up to 3 seconds faster than my patch
(because my patch waits 3 seconds before checking on the number of jobs
that are running).
Greg
next prev parent reply other threads:[~2011-07-14 2:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 1:26 [PATCH 0/3] coccinelle: add parallel execution Greg Dietsche
2011-07-13 1:26 ` [PATCH 1/3] coccinelle.txt: add overview section Greg Dietsche
2011-07-26 14:46 ` Nicolas Palix
2011-07-13 1:26 ` [PATCH 2/3] coccinelle.txt: add documentation of PARALLEL= flag Greg Dietsche
2011-07-27 6:19 ` Nicolas Palix
2011-07-13 1:26 ` [PATCH 3/3] coccicheck: add parallel execution Greg Dietsche
2011-07-13 2:42 ` Joe Perches
2011-07-14 2:14 ` Greg Dietsche [this message]
2011-07-26 13:33 ` Nicolas Palix
2011-07-26 13:53 ` Michal Marek
2011-07-26 22:46 ` Greg Dietsche
2011-07-26 22:36 ` [PATCH v2] " Greg Dietsche
2011-07-27 6:18 ` Nicolas Palix
2011-07-14 9:37 ` [PATCH 0/3] coccinelle: " Ian Campbell
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=4E1E510A.6010005@cuw.edu \
--to=gregory.dietsche@cuw.edu \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@diku.dk \
--cc=joe@perches.com \
--cc=julia@diku.dk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npalix.work@gmail.com \
--cc=rdunlap@xenotime.net \
/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.