On Sun, Nov 15, 2009 at 6:54 AM, Stefan Behnel <[email protected]> wrote: > > Leon Sit, 14.11.2009 15:29: >> The Copperhead project at UCB is aimed to produce code that can be ran >> on CUDA architecture concurrently. Is current Cython design suitable >> to integrate such ideas/projecot in the future or by design, > > Sure, if "such ideas" is referring to code parallelisation. We've been > thinking about integrating OpenMP a while ago, although there hasn't been > any major push in that direction since. The current moves are more towards > a SIMD data type, which would provide a more natural way to introduce > parallelism into the language. > > http://wiki.cython.org/enhancements/simd > > But I actually like the idea of optimising map(). What about writing our > own version of map() that spawns (OpenMP) threads when called on nogil > functions? That's certainly less nice to use than a parallel for-loop, but > it would certainly allow all sorts of fast code... > > Given that you need to constrain the number of parallel executions, it > might be better not to overload Python's own map(), though, but to provide > a "cython.map(f, *iterables, parallel=1)". > > >> they are likely to be a separate project? > > Cython is targeting the C programming language, not the CUDA platform or > OpenCL. So I don't see an interest in *not* being separate projects. >
Stefan, I think you are wrong... Targeting CUDA or OpenCL would be more or less conceptually equivalent to Fortran interoperability and Kurt's work on fwrap. -- Lisandro Dalcín --------------- Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC) Instituto de Desarrollo Tecnológico para la Industria Química (INTEC) Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET) PTLC - Güemes 3450, (3000) Santa Fe, Argentina Tel/Fax: +54-(0)342-451.1594 _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
