> @parallel should automatically do @threads on every compute node. Actually, that should still be under user control. For example, the user may want to use @threads explicitly in an inner loop, or not only want one instance of the loop on every host for some other reason.
On Saturday, July 30, 2016 at 11:14:24 AM UTC+2, Viral Shah wrote: > > As soon as @threads is stable enough for wide usage, @parallel should > automatically do @threads on every compute node. For now, we should > certainly try to get this to work. If not in this form, with a different > macro like @parallelthreads or something. > > -viral > > On Saturday, July 30, 2016 at 12:00:51 PM UTC+5:30, Oliver Schulz wrote: >> >> It would be nice if @parallel and @threads could be combined. E.g. in an >> expression >> >> @parallel @threads for [...] end >> >> could it be possible for @parallel to "forward" @threads to the inner >> loops it produces? Does something like this exist already in some form? >> Forwarding @simd might also be nice in some cases, if technically possible >> (of course @inbounds and @fastmath would need to be "forwarded" too, I >> guess). >> >
