From: Greg Dietsche <gregory.dietsche@cuw.edu>
To: Michal Marek <mmarek@suse.cz>
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: [RESEND 3/3] coccicheck: add parallel execution
Date: Thu, 12 Jan 2012 11:20:11 -0600 [thread overview]
Message-ID: <14fc89a6d23764081dc4e94490fdb8ed@farmergreg.com> (raw)
In-Reply-To: <4EE51709.1030305@suse.cz>
On 12-11-11 02:48pm, Michal Marek wrote:
> On 6.11.2011 03:14, Gregory.Dietsche@cuw.edu wrote:
>> + coccinelle $f>/tmp/cocci_parallel_$$_$PARALLEL_ID 2>&1 &
>
> This opens a symlink race.
>
> And this whole parallel execution should be done by make. Just have a
> generic rule for getting result from a single check, make the default
> target depend on the list of the wanted results and concatenate the
> results there. make -j will then take of parallelizing it.
Michal,
Sorry for the slow response - my mail filters weren't behaving well at
all...
For now, lets just drop this patch. I don't have the time to fix it up.
A few months ago I did take a look at what it would mean to use make's
-j option
and it seemed to me that doing so would require completely changing how
the coccinelle
script works.
I would like to see my M= patch set merged though:
https://lkml.org/lkml/2011/11/5/94
Thanks,
Greg
prev parent reply other threads:[~2012-01-12 17:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 2:14 [RESEND 0/3] coccinelle: " Gregory.Dietsche
2011-11-06 2:14 ` [RESEND 1/3] coccinelle.txt: add overview section Gregory.Dietsche
2011-11-06 18:18 ` Julia Lawall
2011-11-06 2:14 ` [RESEND 2/3] coccinelle.txt: add documentation of PARALLEL= flag Gregory.Dietsche
2011-11-06 18:19 ` Julia Lawall
2011-11-06 2:14 ` [RESEND 3/3] coccicheck: add parallel execution Gregory.Dietsche
2011-11-06 18:20 ` Julia Lawall
2011-12-11 20:48 ` Michal Marek
2012-01-12 17:20 ` Greg Dietsche [this message]
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=14fc89a6d23764081dc4e94490fdb8ed@farmergreg.com \
--to=gregory.dietsche@cuw.edu \
--cc=cocci@diku.dk \
--cc=gilles.muller@lip6.fr \
--cc=julia@diku.dk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome