Hi Bibek --
It's mis-named. I have a rainy-day list item to rename it executeOn,
since that is its Chapel semantics. As it happens the comm layers do
make use of Chapel tasks to implement this on the target locale in some
cases, but from the Chapel point of view it's really moving execution,
not creating parallel execution.
greg
On 5/21/2015 9:37 AM, Bibek Ghimire wrote:
hi there,
I was curious why chapel calls fork for the remote ftable call. Is
there any particular reason to call it fork since fork usually comes
with meaning of creating a process.
-Bibek
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Chapel-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-users
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Chapel-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-users
