From: Michal Marek <mmarek@suse.cz>
To: Nicolas Palix <Nicolas.Palix@inria.fr>
Cc: Greg Dietsche <gregory.dietsche@cuw.edu>,
Joe Perches <joe@perches.com>,
julia@diku.dk, Gilles.Muller@lip6.fr, 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: Tue, 26 Jul 2011 15:53:11 +0200 [thread overview]
Message-ID: <4E2EC6C7.3080009@suse.cz> (raw)
In-Reply-To: <CAAxaTiNJNXnn3PAcKWBSZ2wbMKBDD9yL6pyediEEBHnjNH-uaA@mail.gmail.com>
On 26.7.2011 15:33, Nicolas Palix wrote:
> Hi,
>
> On Thu, Jul 14, 2011 at 4:14 AM, Greg Dietsche<gregory.dietsche@cuw.edu> wrote:
>> 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.
Why not move the loop into some Makefile and let make take care of the
parallel execution? Something among the lines of
results := check1.out check2.out ... (generated)
coccicheck: $(results)
cat $^
%.out: FORCE
... run given test and store its result ...
then the user can simply type make -j6 coccicheck.
Note: I haven't seen the patch, I only got Nicolas' mail now.
Michal
next prev parent reply other threads:[~2011-07-26 13:53 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
2011-07-26 13:33 ` Nicolas Palix
2011-07-26 13:53 ` Michal Marek [this message]
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=4E2EC6C7.3080009@suse.cz \
--to=mmarek@suse.cz \
--cc=Gilles.Muller@lip6.fr \
--cc=Nicolas.Palix@inria.fr \
--cc=cocci@diku.dk \
--cc=gregory.dietsche@cuw.edu \
--cc=joe@perches.com \
--cc=julia@diku.dk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox