Charm++ parallel programming system

["Kale, Laxmikant V" <kale AT illinois.edu>]

Then, are you (the programmer) required to make sure only one of the sdag
methods is active at a time? Otherwise, there is an ambiguity as to which
of them will advance if both flows are waiting  on (i.e.e expecting) the
same entry method.

I'd prefer even a restrictive semantics, as long as it is unambiguous.
-- 
Laxmikant (Sanjay) Kale         http://charm.cs.uiuc.edu
<http://charm.cs.uiuc.edu/>
Professor, Computer Science     
kale AT illinois.edu
201 N. Goodwin Avenue           Ph:  (217) 244-0094
Urbana, IL  61801-2302          FAX: (217) 265-6582


On 12/29/12 1:46 PM, "Phil Miller" 
<mille121 AT illinois.edu>
 wrote:

>I just double-checked, and CharmLU does indeed define the same entry
>method with when clauses in multiple SDAG entry methods. E.g.
>pivotRowSwap() is defined in both factorDiagBlock() and
>factorBelowDiagBlock(), pivotBatchDone() is defined in 3 distinct
>entry methods, and recvSolveData() in 2. This code works without
>trouble.
>
>On Fri, Dec 28, 2012 at 7:47 PM, Phil Miller 
><mille121 AT illinois.edu>
>wrote:
>> That should be just fine. I believe we do it in charm LU, and maybe in
>>amr.
>> Will check when I'm not on my phone.
>>
>> On Dec 28, 2012 7:18 PM, "Kale, Laxmikant V" 
>> <kale AT illinois.edu>
>>  wrote:
>>
>> And to cover another case: you should not haver a single method occur in
>> when blocks of two different sdag entry methods. (please confirm, and
>>add
>> to documentation, one of you).
>>
>>
>>
>> On 12/29/12 1:25 AM, "Phil Miller" 
>> <mille121 AT illinois.edu>
>>  wrote:
>>
>>>On Fri, Dec 28, 2012 at 1:43 P...
>>
>>>_______________________________________________
>>>charm mailing list
>>>charm AT cs.uiuc.edu
>>>http://list...