lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 26 Jul 2011 15:53:11 +0200
From:	Michal Marek <mmarek@...e.cz>
To:	Nicolas Palix <Nicolas.Palix@...ia.fr>
Cc:	Greg Dietsche <gregory.dietsche@....edu>,
	Joe Perches <joe@...ches.com>, julia@...u.dk,
	Gilles.Muller@...6.fr, rdunlap@...otime.net,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	cocci@...u.dk
Subject: Re: [PATCH 3/3] coccicheck: add parallel execution

On 26.7.2011 15:33, Nicolas Palix wrote:
> Hi,
>
> On Thu, Jul 14, 2011 at 4:14 AM, Greg Dietsche<gregory.dietsche@....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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ