charm AT lists.siebelschool.illinois.edu
Subject: Charm++ parallel programming system
List archive
- From: Eduard Llamosí <llamosi.e AT husky.neu.edu>
- To: charm AT cs.uiuc.edu
- Subject: [charm] SADG Issue
- Date: Mon, 25 Feb 2013 13:43:08 -0500
- List-archive: <http://lists.cs.uiuc.edu/pipermail/charm/>
- List-id: CHARM parallel programming system <charm.cs.uiuc.edu>
Greetings,
I'm trying to figure out SADG quirk for a program I'm working on. If we have a definition similar to this one within a chare:
entry void runForever() {
for (iter = 0; iter < nIters; ++iter) {
// Match to only accept inputs for the current iteration
when iterationWork[iter](Input in) {
// Do something
}
}
};
How can we invoke the iterationWork method for a particular iteration? If we simply invoke it like this:
workerProxy.iterationWork(in);
it seems to always invoke iteration 0.
The manual seems to only cover the receiving end of this matter.
Kind regards,
Eduard Llamosi
- [charm] SADG Issue, Eduard Llamosí, 02/25/2013
- Re: [charm] SADG Issue, Jonathan Lifflander, 02/26/2013
Archive powered by MHonArc 2.6.16.