Markus
I imagine that your tool can benefit from distribution of tasks to various threads more than it might lose because of synchronisation costs for parallelisation. How are the chances to reuse any thread pool implementation?
I think Coccinelle should concentrate on doing one thing well and not get side tracked into parallelization of workloads. What is needed is a tool that divides up the work and dispatches it to multiple instances of Coccinelle. I have been reading about how people have been experimenting with Amazon's cloud computing service. It looks relatively cheap and at some point I will investigate it. I am wondering whether to split my eventual 100'ish scripts across multiple nodes or to split the source across the nodes. I guess the 'traditional' Google approach is to split up the data. -- Derek M. Jones tel: +44 (0) 1252 520 667 Knowledge Software Ltd mailto:[email protected] Source code analysis http://www.knosof.co.uk _______________________________________________ Cocci mailing list [email protected] http://lists.diku.dk/mailman/listinfo/cocci (Web access from inside DIKUs LAN only)
